checkout-api p99 latency > 2s
Walkthrough
Watch an alert become an incident.
One alert, walked through the checks above with their default thresholds.
01 · A webhook arrives
{
"alert_type": "error",
"title": "checkout-api p99 latency > 2s",
"host": "checkout-api-canary",
}02 · The alert gets a fingerprint
- fingerprint
- organization · source · dedup key
The alert’s dedup key or identity, falling back to its title. The service is not an input.
- dedup
- open incident
A repeat joins the incident that is still open for it: at any age when the sender supplies its own dedup key, within 24 hours when the identity is only the title or e-mail subject.
03 · Duplicates collapse, grouping does not cross sources
- repeats
- same fingerprint
Attach to the open incident with no new page. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages.
- title grouping
- title similarity ≥ 0.6
Same source, same service, still Triggered, within 600s. Never across sources.
04 · Severity is the source's, plus a suggestion
- incident severity
- P1
Mapped from what Datadog sent (or an orchestration override).
- suggestion
- P1, matched “latency”, “p99”
A separate suggestion from a keyword ruleset and your resolved incidents. A person applies it; it never changes severity on its own.
05 · Routed and paged
How incident severity levels work →What an escalation policy is →How severity suggestions are calculated →