Incident search with @incident

Earlier this year, we launched @incident which opened up loads of new ways that responders could interact with our product. Now, we’ve added a new capability, which allows for incident search with @incident .

You can now ask questions such as:

• Have we seen incidents like this before?
• Did we have an incident about high database CPU in February?
• What other incidents have affected customer X?

All customers with our chatbot enabled can now start asking either by tagging @incident in Slack or going direct to the Chat tab in the dashboard.

Please note, we will never search for private incidents, these will always remain ‘invisible’ to @incident.

Merge pending alerts when merging incidents

Previously, if you merged incident A into incident B, and incident A had pending grouped alerts (alerts you never confirmed as part of that incident), we would create an entirely new incident C with those pending alerts.

Now, as part of merging, we'll ask what you want to do with these existing alerts, giving you the option to include them into the merged incident. We've also added a handy "Attach all" button, as previously you had to click through each alert and mark it as related.

What else we’ve shipped