Supabase and ClickHouse Connection Exhaustion
criticalConnection ManagementUpdated Feb 23, 2026
AgentOps backend relies on Supabase (PostgreSQL) for authentication and ClickHouse for analytics. Misconfigured connection pools or lack of connection reuse can exhaust database connections under load, causing agent traces and metrics to fail silently.
Technologies:
How to detect:
Monitor database connection pool utilization (active, idle, waiting) for both Supabase and ClickHouse. Alert when pool exhaustion occurs (e.g., >90% active connections) or when database connection errors spike in API or dashboard logs.
Recommended action:
Increase connection pool size, enable connection pooling (e.g., PgBouncer for Supabase), implement connection timeout and retry logic, monitor connection lifecycle, and ensure connections are properly closed after use. Add circuit breakers for database clients.