As a developer of notify, I only want to be alerted when there are actionable errors that are encountered in the system so that we can maintain focus on day to day work and decrease alert fatigue.
WHY are we building?
There are errors that occur in celery that do not require intervention from us (Duplicate key constraints as an example.) Currently, these alerts cause critical alarms in notification-ops, but there is nothing for us to do in these cases.
WHAT are we building?
Refine the alerts to exclude expected errors (within reason - perhaps a threshold increase)
VALUE created by our solution
Close to the business, what's the value?
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Description
As a developer of notify, I only want to be alerted when there are actionable errors that are encountered in the system so that we can maintain focus on day to day work and decrease alert fatigue.
WHY are we building?
There are errors that occur in celery that do not require intervention from us (Duplicate key constraints as an example.) Currently, these alerts cause critical alarms in notification-ops, but there is nothing for us to do in these cases.
WHAT are we building?
Refine the alerts to exclude expected errors (within reason - perhaps a threshold increase)
VALUE created by our solution
Close to the business, what's the value?
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Privacy considerations
Security controls in place
Measuring success and metrics
QA Steps