Skip to content
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

Closed
2 tasks done
JonellaCulmer opened this issue May 19, 2020 · 4 comments
Closed
2 tasks done

Error handling and alerting for MURs that are missing documents #4364

JonellaCulmer opened this issue May 19, 2020 · 4 comments

Comments

@JonellaCulmer
Copy link
Contributor

JonellaCulmer commented May 19, 2020

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:

  • When reloading MURs, API should show a warning message when there are missing documents.
  • Celery should send a Slack alert once a day when there are missing documents in production.
@JonellaCulmer JonellaCulmer added this to the Sprint 12.4 milestone May 19, 2020
@lbeaufort lbeaufort changed the title Error handling for MURs that are missing documents Error handling and alerting for MURs that are missing documents during reload Jun 10, 2020
@patphongs patphongs modified the milestones: Sprint 13.4, Sprint 13.5 Aug 31, 2020
@patphongs
Copy link
Member

Moving this for now so we can do the Slack alerting later

@jason-upchurch jason-upchurch removed this from the Sprint 13.7 milestone Nov 3, 2020
@JonellaCulmer JonellaCulmer added this to the Sprint 14.2 milestone Mar 2, 2021
@JonellaCulmer JonellaCulmer changed the title Error handling and alerting for MURs that are missing documents during reload Error handling and alerting for MURs that are missing documents Mar 4, 2021
@rfultz rfultz added this to the Sprint 14.5 milestone Apr 6, 2021
@patphongs patphongs modified the milestones: Sprint 14.6, Sprint 15.1 Apr 29, 2021
@patphongs patphongs modified the milestones: Sprint 15.1, Sprint 15.4 Jun 2, 2021
@lbeaufort lbeaufort modified the milestones: Sprint 15.4, Sprint 15.5 Jul 28, 2021
@patphongs patphongs modified the milestones: Sprint 15.5, Sprint 15.6 Jul 28, 2021
@patphongs
Copy link
Member

Moved to 15.6 due to resource constraints

@lbeaufort
Copy link
Member

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.

@lbeaufort lbeaufort removed this from the Sprint 16.1 milestone Sep 30, 2021
@pkfec
Copy link
Contributor

pkfec commented Apr 13, 2023

Case document refresh window has been updated in this PR #5241

Slack alerts have been setup on legal-source and bots` channel when legal documents are updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants