ReliabilityAdvanced
Quantify declared incident impact
How many accounts and operations were affected by each declared incident?
Reduce service events to an account-and-incident grain before adding incident severity and account revenue context.
The dataset and query remain in this browser.
Published 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.
- Represented revenue is communication context, not a severity formula or a contractual damages calculation.
Decisions the SQL cannot make
- 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.