incident.io: an investigation for every new incident
Teams that run incidents in incident.io can now have Polylane investigate each new incident in its Slack channel, and send escalations to on-call through their own alert routes.
What changed
Connect incident.io with one API key. Every new live incident starts a Polylane investigation; private and test incidents are skipped. When
Slack is connected to the same workspace, Polylane joins the incident channel and posts its findings there, and replies in that channel go to the same investigation.
Polylane sets up incident.io for you: on connect it creates a workflow, a workflow secret and an HTTP alert source named "Polylane", and disconnecting deletes all three. incident.io does not resend a failed notice, so Polylane also checks for live incidents every five minutes.
Escalations page through your routes
When Polylane cannot resolve an issue, it raises an escalation. Escalations at or above the level you set, high by default, go to the Polylane alert source, and your alert routes decide who is paged. Marking the escalation handled resolves the alert.
Polylane also adds your incident.io catalog services to the context graph and links them to their repositories. See the incident.io integration.
Why it matters
During an incident, the team works in the incident channel. When the investigation starts on its own and reports there, the evidence arrives where people already are, and nobody has to open another tool to ask for it.
How to use it
- In incident.io, open Settings → API keys and create a key with the
viewerrole, plusworkflows_editorandsecrets_managefor investigations andon_call_editorfor escalation alerts. - In the Polylane console, open Settings > Integrations, connect incident.io and paste the key. Polylane names the role any feature is missing.
- In incident.io, add the Polylane alert source to an alert route. Until you do, escalation alerts page no one.