Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T308467 implementing an incident response workflow automation tool for SRE | |||
Resolved | Eevans | T356790 Corto: Incident responder workflow automation (MVP) | |||
Resolved | Eevans | T370783 corto: implement resolve incident |
Event Timeline
Comment Actions
Resolved maps well to our docs on resolving an incident, https://wikitech.wikimedia.org/wiki/Incident_response/Runbook#To_resolve_the_incident_and_stop_being_IC
How would "incident issue closed" differ? My apologies if these state definitions are listed somewhere.
Comment Actions
I was thinking in terms of application state management rather than process - what does telling corto that an incident is resolved change? Resolving or setting stalled on the phab task seems like a decent solution for this
Comment Actions
ah, thanks for the explanation. With regards to state management, I think marking an incident as resolved in corto should:
- Resolve the incident in phabricator, this state should be used as the authoritative source for the incident status
- Mark it as resolved in the google doc
- Mark it as resolved on wikimediastatus.net, if a public post was created?