Statping: Incident management

Created on 11 Jun 2019 · 6Comments · Source: statping/statping

What would you like on Statping?

When there is an incident affecting service, I'd like to be able to write a message about the incident, and update it as the incident is resolved. This way, our users can be informed about the impact of an incident, that we're working on it, and when it can be expected to be resolved.

Describe the solution you'd like

See an example incident on Github's status page
An incident should have a current status; with possible values Investigating (aware of problem), Monitoring (fix is implemented), Resolved (fix is verified)
An incident should have an impact value; Critical, Major, Minor
The incident should be automatically timestamped on creation, and with each update
The incident should be very visible when active
The incident should be easy to find even after the incident is resolved, so users can quickly know when it has been resolved and review past incidents
It should be possible to notify users when the incident is created and updated

Describe alternatives you've considered

The existing Messages feature is close enough to be considered an alternative, however:

It doesn't have the affordances for information that is important for an incident (status, impact, timeline)
That is helpful because incident response is a stressful and time sensitive activity
A message doesn't seem to be easy to find after it has concluded

Is your feature request related to a problem? Please describe.

Since Statping is the place to see whether services are working or not, it makes sense that it should include further information about incidents that impact those services being available. Having these in one place is valuable to users.

Additional context

N/A

feature

Source

asavoy

👍1

Most helpful comment

Hey @asavoy , great feature request. I've begun working on this and it shows sample data in the latest version. Below is a checklist of the tasks needed for this feature.

Tasks

[x] View Incidents for a service from within service view
[x] View incident updates for each incident
[ ] Add a form to create an incident for a service
[ ] Create form inside an incident to append Incident Updates
[x] /api/incidents GET endpoint to show all incidents
[x] /api/incidents POST endpoint to create new incidents
[x] /api/incidents/{id}/update POST endpoint to add an update to incident
[x] /api/incidents/{id} DELETE endpoint to remove incidents
[ ] /api/incidents/{id}/update/{uid} DELETE endpoint to remove an incident update

hunterlong on 25 Jun 2019

❤12

All 6 comments

Hey @asavoy , great feature request. I've begun working on this and it shows sample data in the latest version. Below is a checklist of the tasks needed for this feature.

Tasks

[x] View Incidents for a service from within service view
[x] View incident updates for each incident
[ ] Add a form to create an incident for a service
[ ] Create form inside an incident to append Incident Updates
[x] /api/incidents GET endpoint to show all incidents
[x] /api/incidents POST endpoint to create new incidents
[x] /api/incidents/{id}/update POST endpoint to add an update to incident
[x] /api/incidents/{id} DELETE endpoint to remove incidents
[ ] /api/incidents/{id}/update/{uid} DELETE endpoint to remove an incident update

hunterlong on 25 Jun 2019

❤12

Any Status Updates?
Can we help you implementing that Feature?

l0nax on 13 Sep 2019

I would like to see those features implemented as well. It would also be a great addition if you can create a service incident yourself.

Please let us know what we can do.

teunis90 on 11 Nov 2019

Hello,

would you accept a pull requests for incident management, can I contribute to it in any way? Or are you already well into the tasks and are set on completing them? I only ask because the issue has been opened quite a few months ago.

Best regards