-
-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new Sentry.capture_check_in
API for Cron monitoring
#2117
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2117 +/- ##
==========================================
+ Coverage 97.41% 97.48% +0.06%
==========================================
Files 85 88 +3
Lines 3294 3382 +88
==========================================
+ Hits 3209 3297 +88
Misses 85 85
|
f48f9c1
to
1b0377e
Compare
1b0377e
to
ef758e4
Compare
ef758e4
to
79abdbe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me, I'm just worried about all the places CodeCov calls out as being uncovered.
codecov is off, just ignore it, a lot of those lines are covered |
79abdbe
to
26557d8
Compare
Oh, and please get the codecove stuff fixed. You'll likely want to do something similar to https://github.com/getsentry/sentry/blob/master/codecov.yml#L61-L63. |
c2f266f
to
045578a
Compare
* New `CheckInEvent` class for the envelope payload * New `Cron::MonitorConfig` class that holds the monitor configuration * New `Cron::MonitorSchedule` module that holds two types of schedules `Crontab` and `Interval`
045578a
to
fb9bc77
Compare
CI will be fixed separately, codecov is now fixed so i'm merging |
end | ||
|
||
describe '.from_interval' do | ||
it 'returns nil without valid unit' do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sl0thentr0py would you consider having this raise instead? Maybe just in development/test?
I spent way too long trying to work out why this wasn't reporting properly:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in general, as a principle, we don't raise in the Sentry SDK since we are an error monitoring service and we don't want to raise our own errors.
I could add debug logs if you wish.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha yes that makes a lot of sense 😂
Logging would be amazing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tracking #2456
CheckInEvent
class for the envelope payloadCron::MonitorConfig
class that holds the monitor configurationCron::MonitorSchedule
module that holds two types of schedulesCrontab
andInterval
part of #2090