RedisMetricclient_backend_max
Maximum number of open connections allowed in the pool
OpenTelemetry (1)Summary
Tracks the maximum number of client backend connections configured or allowed. This represents the upper limit for concurrent connections from client applications to Redis. Monitoring this metric against current connection counts helps detect approaching capacity limits, which can lead to connection rejection and application failures if exceeded.
Interface Metrics (1)
OpenTelemetry
Knowledge Base (1 documents, 0 chunks)
Technical Annotations (4)
Configuration Parameters (1)
max_connectionsrecommended: 100 for smaller instancesError Signatures (1)
too many connectionserror codeTechnical References (2)
PgBouncercomponentProxySQLcomponentRelated Insights (4)
High bolt connections combined with client backend wait time indicates connection pool exhaustion, causing clients to queue for available connections and degrading application response times.
High client_backend_wait_time combined with low client_backend_usage indicates application connection pool misconfiguration or excessive connection churn, even when database-side cloudsql_googleapis_com/database/network/connections appears normal.
When client_backend_create_time and client_backend_wait_time are elevated, new connections are queuing because the instance is saturated with connection requests. This often precedes connection pool exhaustion and instance instability.