What one row represents
One affected account per incident after request outcomes are pre-aggregated.
Decision this helps you make
Scope remediation and communication using observed impact without treating revenue as a measure of customer importance.
Metric definitions
Put the denominator and units beside the chart
Use your own field names, but keep the same definition of one row. Check the linked schema before mapping your production events.
- Affected accounts
- Failed operations
- Affected regions
- Represented monthly revenue
failed operations
Demonstration data, not a customer result or benchmark
Review the query before adapting the fields
Adapt this query to your events before using it in production. Set a time range and environment filter, decide how to handle incomplete time buckets, and require enough events for a useful comparison.
WITH account_impact AS (
SELECT
incident_id,
account_id,
COUNT(*) AS impacted_operations
FROM service_events
WHERE incident_id IS NOT NULL
AND status = 'error'
GROUP BY incident_id, account_id
)
SELECT
i.incident_id,
i.severity,
COUNT(*) AS affected_accounts,
SUM(ai.impacted_operations) AS failed_operations,
SUM(a.monthly_revenue_usd) AS represented_mrr_usd
FROM account_impact ai
JOIN incidents i USING (incident_id)
JOIN accounts a USING (account_id)
GROUP BY i.incident_id, i.severity
ORDER BY failed_operations DESC;Check these before publishing the result
- The incident identifier is assigned from a reviewed incident window.
- Failed operations use stable account identifiers and exclude synthetic traffic.
- Revenue context comes from an approved account dimension.
Check the query and metric definitions
- Pre-aggregate operations before joining account and incident dimensions.
- Compare distinct affected accounts with the joined row count.
- Preserve the incident definition and query window with the result.
What the results mean
What this result cannot prove by itself
Represented revenue helps prioritize communication; it does not make lower-revenue customers less important or establish contractual impact.
Related dashboard examples
SaaS health overview
Did account adoption, application reliability, or represented revenue change enough to require a deeper review?
Inspect exampleAPI reliability and latency
Which endpoints have rising error rates or p95 latency, and enough requests to trust the comparison?
Inspect exampleLLM usage and unit economics
Which model-backed workflow consumes the most estimated cost per successful outcome?
Inspect exampleValidate the definition with known data
Test the query with known successes, failures, missing values, duplicates, and values at its limits. Check the results before using it in a production dashboard or alert.