fix: Wrap disable_uptime_monitor in a transaction for broken_monitor task #91989
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to fix instances where the broken monitor checker would leave uptimes in an inconsistent / broken state and then prevent them from being fixed / run again.
Within disable_uptime_monitor we are setting the uptime status to be "OK" in the middle of the disable function
sentry/src/sentry/uptime/subscriptions/subscriptions.py
Lines 356 to 358 in eeff1fd
The task relies on the UptimeSubscription have "failed" status here:
sentry/src/sentry/uptime/subscriptions/tasks.py
Lines 231 to 234 in 81a042a
If the disable job fails / exists early / etc. before actually running through everything, this would leave broken monitors in potentially a worse state than before. Looking at all the other usages of disable / enable_uptime_monitors, they seem to be wrapped in a transaction one level above the call site, so I did something similar here.
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.