-
Notifications
You must be signed in to change notification settings - Fork 106
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
Error handling and alerting for MURs that are missing documents #4364
Comments
Moving this for now so we can do the Slack alerting later |
Moved to 15.6 due to resource constraints |
Partially addressed by #4957 - we need to have a larger conversation about the best technical approach to these alerts. After checking with @fec-jli and @patphongs I'm going to put this back in "new issues" and re-prioritize this work if it the issue re-occurs. |
Case document refresh window has been updated in this PR #5241 Slack alerts have been setup on |
What we're after:
To catch missing MUR documents in the future, we need to incorporate better error handling and alerting when an error occurs in production. We currently get emails to the database team, but adding slack would put more eyes on this high-impact issue.
For more details:
This is related to #4361
Completion criteria:
The text was updated successfully, but these errors were encountered: