[IMPROVEMENT] Tracking for failed alerts #200
Merged
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.
Even though Promgen is instrumented with Sentry, users need a way to know if their alerts are being sent properly. While a more robust retry mechanism will be attempted in the future this should give more visibility into the current state
error_count
andsent_count
to Alert model for trackingAlertError
log for tracking failed messagestasks.send_alert
to better log errors and increment countersFuture work to make sender.test more aware to avoid special casing the alert_pk check in
tasks.send_alert