ReliabilityAdvanced
Quantify declared incident impact
How many accounts and operations were affected by each declared incident?
Group service events by account and incident. Then join incident severity and account revenue.
The dataset and query remain in this browser.
Expected result
Failed operations by declared incident
inc_checkout_latency
64
64
inc_worker_retries
45
45
| incident_id | severity | affected_accounts | impacted_operations | failed_operations | represented_mrr_usd |
|---|---|---|---|---|---|
| inc_checkout_latency | sev_2 | 6 | 180 | 64 | 5,898 |
| inc_worker_retries | sev_2 | 5 | 75 | 45 | 5,898 |
How to read the query
- The CTE prevents many service events from multiplying account revenue when the dimensions are joined.
- Affected account count and failed operations distinguish breadth from repeated impact.
- Revenue shows which accounts the incident affected. It does not measure severity or damages.
How to interpret the results
- 1Define the impact rule that associates an operation with a declared incident.
- 2Keep free, low-revenue, and internal accounts visible even when prioritizing outreach.
- 3Reconcile the event-derived list with support cases and status-page communications.
Related lessons
Keep the result
Run this query on your own events
Create a free workspace only when you are ready to save the query, connect real events, and monitor the result. No credit card is required.