-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update our Incident Response process and Slack workflow #3478
Labels
Comments
dfitchett
added
VRO-team
needs-refinement
needs refinement before it's ready to work
labels
Sep 18, 2024
bianca-rivera
changed the title
Incident Response Workflow - Add Impact Section
Update the Incident Response Workflow
Sep 23, 2024
31 tasks
bianca-rivera
changed the title
Update the Incident Response Workflow
Update our Incident Response process and Slack workflow
Oct 1, 2024
Note: I'm on this issue as part of my onboarding to help learn about the VRO on-call process 😄 |
bianca-rivera
removed
the
needs-refinement
needs refinement before it's ready to work
label
Oct 10, 2024
6 tasks
made more significant updates and formatting changes; added new AC bullet to share with VRO team before sending message to partner teams of latest update regarding impact metrics and include highlighting any other substantial changes |
Excellent job, @bianca-rivera !!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As the on-call engineer for the VRO platform team, I need as many tasks automated as possible to reduce the risk of missing manual follow-ups. Specifically, I want to update our existing Incident Response process and Slack workflow to automatically incorporate the new step of reaching out to partner teams to assess how our downed services impacted their processes and, ultimately, the veterans we serve. This will ensure that we are documenting the effects of failures on the VRO platform and reduce the potential for silent failures.
AC
SEV 1
andSEV 2
incidentsResources
Reference Incidents Epic
The text was updated successfully, but these errors were encountered: