You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the slack event handlers provided by response, it would be great to take actions on the opening, closing or comms channel creation for an incident.
These are the sorts of things we'd like to be able to do.
Add a link to our runbooks as the first message in the incident channel.
Ask incident leads to organise a 5-whys at the end of the incident.
Alert #general with a quick summary when impacts are set/changed.
Currently, I don't believe (although happy to be corrected!) that there's a good place to put these. I'm sure something could be hacked together with the cron, but it would be nice to have a set of APIs to handle these.
Here's roughly what I think it could look like:
@incident_closeddeffive_whys_reminder(incident: Incident) ->None:
channel=incident.comms_channel()
ifchannelisNone:
returnchannel.post_message("Please organise a 5-Whys")
If this feature would be a good addition I'm happy to have a stab at the first pass at some point, but it would be great to get some feedback on the idea.
The text was updated successfully, but these errors were encountered:
@danpalmer Django signals are a nice generic way of doing this - essentially we can write handlers which hook into various stages of the model lifecycle, e.g. handling updates to models before or after saving them.
We can also define our own custom signals - this would be an easy way to achieve the @incident_closed annotation you've defined above. Actually, I think this would be a great idea, and a nicer interface for people to use rather than hooking directly into model update signals.
@milesbxf great idea, I hadn't considered signals. I agree that defining new signals would probably be a better idea here, the model change events might be tricky to decode exactly what's changing. I'll have a go at implementing this sometime. Will update here before I do though in case anyone else wants to take a look first.
In addition to the slack event handlers provided by response, it would be great to take actions on the opening, closing or comms channel creation for an incident.
These are the sorts of things we'd like to be able to do.
Currently, I don't believe (although happy to be corrected!) that there's a good place to put these. I'm sure something could be hacked together with the cron, but it would be nice to have a set of APIs to handle these.
Here's roughly what I think it could look like:
If this feature would be a good addition I'm happy to have a stab at the first pass at some point, but it would be great to get some feedback on the idea.
The text was updated successfully, but these errors were encountered: