Database Status
Connection pool metrics for the Config DB (PostgreSQL) and Results DB (TimescaleDB). Shows pool utilization, active/idle connections, waiting queries, and query latency. Pool exhaustion causes queries to queue, degrading performance across the entire system.
Fields & Columns
| Name | Description |
|---|---|
| Connection Pool | Current connections vs. maximum pool size, shown as a count and percentage |
| Active / Idle | Active connections are running queries; idle connections are available for immediate use |
| Waiting Queries | Queries waiting for a free connection — should always be 0 in normal operation |
| Query Latency | Round-trip time for a simple health-check query. Green under 20ms, yellow 20-100ms, red over 100ms |
| Pool Utilization | Visual bar showing what percentage of the connection pool is in use. Red above 80% |
Gotchas
- Any waiting queries indicate all pool connections are busy. Investigate slow queries or increase the connection pool size via the DB_POOL_MAX environment variable in the service configuration.
- The Results DB (TimescaleDB) handles high-volume scan data and typically shows higher utilization than Config DB.
- The Jobs DB is not shown here because it is accessed by the dispatcher, not by the manager service.
API Calls (1)
| Method | Path | Description |
|---|---|---|
| GET | /api/health/infra/db-status | Fetch connection pool stats for Config and Results databases |