Database reliabilityBeginner
Measure database connection-pool saturation
Which service is exhausting its database connection pool?
Rank services by maximum pool use, acquisition wait, and timeout samples.
The dataset and query remain in this browser.
Published expected result
Maximum connection-pool saturation
checkout
100%
100%
worker
100%
100%
api
41.7%
41.7%
| service | max_saturation_pct | average_acquire_wait_ms | timeout_samples |
|---|---|---|---|
| checkout | 100 | 124.3 | 1 |
| worker | 100 | 157.5 | 1 |
| api | 41.7 | 8.5 | 0 |
How to read the query
- Pool saturation normalizes active connections against each service's configured limit.
- Acquisition wait catches pressure before requests begin timing out.
- Timeout samples distinguish sustained contention from harmless utilization spikes.
Decisions the SQL cannot make
- 1Profile slow or long-held transactions before increasing the pool limit.
- 2Check the database connection ceiling before changing application pool sizes.
- 3Alert on sustained wait and timeout behavior, not utilization alone.
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.