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

Clarify difference between statuses in incident response plan #3579

Open
AetherUnbound opened this issue Dec 22, 2023 · 0 comments
Open

Clarify difference between statuses in incident response plan #3579

AetherUnbound opened this issue Dec 22, 2023 · 0 comments
Assignees
Labels
📄 aspect: text Concerns the textual material in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: documentation Related to Sphinx documentation

Comments

@AetherUnbound
Copy link
Collaborator

Description

The current set of statuses for an incident leave some confusion around which status is appropriate to move to after Stabilization pending.

Quoted from the discussion here:

@sarayoufriend:
What's the difference between stabilized and under investigation? Is that to allow specific time after stabilisation where we haven't started looking into the root cause?

@stacimc:
I also had this question. Per the new text added below:

Some incidents may not require further investigation once they are stabilized and can be immediately resolved.

But I think those incidents would go Stabilization pending straight to Resolved, so I'm still not sure when something would be Stabilized but not Under investigation. I guess it implies that investigation is needed but not started? Or, possibly, investigation has already happened and the cause is identified but not yet fixed? Although that can't be right, because that's the definition of Resolved given below.

If Resolved is updated to mean that the long-term fixes are implemented, then one interpretation of the statuses which would maybe make sense is:

  • Stabilization pending: actively disrupting service
  • Under investigation: stabilized but not resolved. Root causes are being researched.
  • Stabilized: Root causes identified but not yet fixed
  • Resolved: Long-term fixes applied

But then the name stabilized feels like an inadequate description 😓

Additional context

Came from discussion around the initial incident response plan in #2679

@AetherUnbound AetherUnbound added ✨ goal: improvement Improvement to an existing user-facing feature 📄 aspect: text Concerns the textual material in the repository 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: documentation Related to Sphinx documentation labels Dec 22, 2023
@AetherUnbound AetherUnbound self-assigned this Dec 22, 2023
@openverse-bot openverse-bot moved this to 📋 Backlog in Openverse Backlog Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📄 aspect: text Concerns the textual material in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: documentation Related to Sphinx documentation
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant