Hear about it first
Alert rules check every minute and notify the channels you chose, with a message when the rule fires and another when it recovers.
Solutions
From the first alert to the written postmortem, in one workspace.
When something breaks, the person on call needs the alert, the affected services, the traces and logs, and somewhere to write down what they find. Onyx Insights keeps those together.
What you get
Narrow it down
Start at Services to see what is unhealthy, use Topology to see what it calls, then open the failing traces and the logs written during them.
Write it down as you go
Investigations collect the evidence. Incidents carry a severity, a commander, status updates and a postmortem.
How a response runs
A rule fires
The rule opens an incident for the affected service and notifies its channels.
You look around
Services and Topology show what is unhealthy and what it depends on. Traces and Logs show what happened.
You record it
A critical incident opens an investigation. Add notes and a hypothesis, and update the incident's status.
It closes
The rule resolves the incident when the condition clears, or an admin resolves it. A postmortem can be written on the incident.
Try an incident from alert to resolution.
Create a rule in a trial workspace and watch it open one.