First look: behind the scenes building an AI incident responder.
Hello, is it me you’re looking for?
August 16, 2021
We've added filtering so you can more easily find the incidents you're interested in.
On the incidents page, we've still got the free text search, but have added some more filtering options. This enables you to look at incidents with particular characteristics; either to find a particular incident or to help do some high level analysis. We also think this might be useful for running regular incident reviews and for anyone wanting an 'at-a-glance' view of the activity over the last week or month.
Currently you can filter by:
- Date — when did the incident happen?
- Severity — what severity did you assign to the incident?
- Status — what is the current status of the incident?
- Participant(s) — who was involved in the incident?
- Any custom fields that you've defined
There'll be more filtering options coming soon - please let us know what you'd like to see next!
What we shipped
New
- You can now pin a message in an incident channel by reacting to it with various pin-like emojis (📌, 📍, 🔖, 💭, ⭐)
Improvements
- We've given the 'update roles' modal a new look so it's a bit easier to use.
- 👷🏽♀️ We spent some time working on improving some fundamentals under the hood, particularly around our API.
Bug fixes
- When updating incident roles via /incident roles, mandatory roles are now actually mandatory.
- We can now gracefully handle it if someone tries to use the same option value twice when adding a custom field.
- The insights section of the dashboard will now recalculate when you open or close an incident, so you won't see out of date information!
P.S. I really wanted to call this blog post ge-filter fish, but we decided that too few people would understand the reference. This post-script was the compromise.