Row grain
One row per active account before the final portfolio-level aggregation.
Decision supported
Choose the component dashboard to inspect; do not make a product or incident decision from the composite preview alone.
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.
- Active accounts
- Successful milestones
- API error rate
- Monthly revenue represented
health index
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_activity AS (
SELECT
account_id,
COUNT(*) AS successful_milestones
FROM product_events
WHERE status = 'success'
GROUP BY account_id
),
account_reliability AS (
SELECT
account_id,
COUNT(*) AS requests,
SUM(CASE WHEN status = 'error' THEN 1 ELSE 0 END) AS errors
FROM api_requests
GROUP BY account_id
)
SELECT
COUNT(*) AS active_accounts,
SUM(a.successful_milestones) AS successful_milestones,
ROUND(100.0 * SUM(r.errors) / NULLIF(SUM(r.requests), 0), 2)
AS api_error_rate_pct,
SUM(ac.monthly_revenue_usd) AS represented_mrr_usd
FROM account_activity a
JOIN account_reliability r USING (account_id)
JOIN accounts ac USING (account_id);Prove these before publishing the result
- Product and request tables use the same pseudonymous account identifier.
- Account revenue is current dimension data, not a historical invoice ledger.
- The newest partial UTC day is excluded from period comparisons.
Checks that keep the dashboard trustworthy
- Pre-aggregate milestones and requests to the account grain before joining.
- Validate unmatched accounts on every side of the join.
- Label represented MRR as prioritization context rather than incident loss.
Interpretation boundary
What this result cannot prove by itself
Treat the score as navigation, not truth. Open the component metric before attributing movement to product adoption or reliability.
Related dashboard examples
API reliability and latency
Which sufficiently busy endpoint has the broadest error or tail-latency regression?
Inspect exampleIncident customer impact
Which accounts and operations were directly represented in a declared incident window?
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.