Database reliabilityAdvanced
Measure database impact by customer plan
Which customer plans are affected by database errors?
Join database operations to account dimensions to quantify the customer impact of failures.
The dataset and query remain in this browser.
Published expected result
Failed database operations by plan
business
0
0
free
1
1
growth
1
1
starter
1
1
| plan | operations | failed_operations | failed_accounts | average_duration_ms |
|---|---|---|---|---|
| business | 4 | 0 | 0 | 265 |
| free | 1 | 1 | 1 | 210 |
| growth | 6 | 1 | 1 | 333.3 |
| starter | 5 | 1 | 1 | 167 |
How to read the query
- The account dimension turns an infrastructure symptom into customer-impact evidence.
- Distinct failed accounts prevents a noisy customer from dominating the affected-account count.
- Plan segmentation supports prioritization without exposing individual customer names.
Decisions the SQL cannot make
- 1Escalate failures affecting paid plans or multiple distinct accounts.
- 2Compare affected-account count with raw operation count before declaring broad impact.
- 3Use the account identifier only for authorized incident follow-up and customer communication.
Continue from this lesson
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.