This one goes out to our power users — we're dropping fire this week in the form of a command palette, a.k.a. CMD+K. This is a powerful keyboard driven menu that allows you to respond to incidents at the speed of thought. It's a great way to quickly search, navigate & perform actions on incidents, without having to use your mouse.
We recently rolled out triage incidents, for when there’s potential to be an incident, but you need to confirm it first. Today, we’ve built on them, adding more features and customisability.
You can now choose how you’d like Triage Incidents to be announced within your Announcement Rules. Either: always show them, hide them completely, or hide them only after they’ve been rejected or merged into another incident.
Incident triggers are the things that cause incidents to be created. They can be things like PagerDuty & OpsGenie, with more coming soon. When an incident trigger is fired, it will be automatically grouped into an existing incident if it matches the incident's trigger rules. If it doesn't match any existing incidents, a new incident will be created.
When configuring an incident trigger, e.g. a PagerDuty incident, there is now much greater control over how an incident will be created. Defaults such as: name, summary, type, severity as well as custom fields can be configured based on properties of the incident trigger, e.g. the PagerDuty service.
Additionally, when closing an incident, if there are any unacknowledged incident triggers. You’ll be prompted to group them into the existing incident, or mark them as unrelated, creating a new incident for them.