Technologies/Redis/redis.connections.rejected
RedisRedisMetric

redis.connections.rejected

Number of connections rejected due to maxclients
Dimensions:None
Available on:OpenTelemetryOpenTelemetry (1)Native (1)DatadogDatadog (1)PrometheusPrometheus (1)

Summary

Counts connection attempts rejected because Redis reached its maxclients limit. Any non-zero value indicates capacity issues — the server cannot accept new clients because all connection slots are occupied. This triggers the connection rejection cascade insight: rejected connections cause application errors, which trigger retries, further increasing rejection rates. Immediate remediation requires either increasing maxclients or identifying and terminating leaked/idle connections.

Interface Metrics (4)
OpenTelemetryOpenTelemetry
Number of connections rejected due to maxclients
Dimensions:None
Native
Number of connections rejected because of maxclients limit
Dimensions:None
DatadogDatadog
Connections rejected due to maxclients
Dimensions:None
PrometheusPrometheus
Connections rejected due to maxclients
Dimensions:None
Related Insights (2)
Redis Connection Pool Starvation from Blocking Patternswarning

When async endpoints make synchronous Redis calls, they hold connections longer than necessary while blocking the event loop, causing artificial connection pool exhaustion even when Redis server capacity is available.

Connection Rejection Cascade From Maxclient Saturationcritical

When Redis reaches maximum client connections (redis.connections.rejected increasing), new connection attempts fail silently while existing connections continue working normally, creating intermittent failures that are difficult to diagnose from application metrics alone.