Row grain
One affected account per incident after request outcomes are pre-aggregated.
Decision supported
Scope remediation and communication using observed impact without treating revenue as a measure of customer importance.
Metric contract
Put the denominator and units beside the chart
Adapt these names to your contract while preserving the declared grain. Inspect the linked event schema before mapping fields from production producers.
- 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
This public query is a starting definition. Add a bounded time filter, complete-bucket policy, environment, and minimum volume appropriate to your production event contract.
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;Prove 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.
Checks that keep the dashboard trustworthy
- 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.
Interpretation boundary
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 sufficiently busy endpoint has the broadest error or tail-latency regression?
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
Run a fixture with known success, failure, missing, duplicate, and boundary cases before connecting the query to a production dashboard or alert.