Technologies/NGINX/nginx_upstream_peers_unavail
NGINXNGINXMetric

nginx_upstream_peers_unavail

How many times the server became unavailable for client requests (state "unavail") due to the number of unsuccessful attempts reaching the max_fails threshold.
Dimensions:None
Available on:DatadogDatadog (1)
Interface Metrics (1)
DatadogDatadog
How many times the server became unavailable for client requests (state "unavail") due to the number of unsuccessful attempts reaching the max_fails threshold.
Dimensions:None
Sources
nginx.upstream.peers.unavailgithub.com
Related Insights (2)
KeepAlive Misconfiguration Exhausts Connectionswarning

KeepAliveTimeout set too high causes idle connections to consume worker threads/processes, reducing effective concurrency. KeepAliveTimeout set too low forces excessive TCP handshakes, increasing latency. Optimal values depend on traffic profile: APIs need 2-5s, static content 5-15s.

▸
Upstream Connection Pool Saturation Blocks NGINX Workerscritical

When NGINX proxies to backends (PHP-FPM, FastCGI, uwsgi) without proper connection limits, a single site can exhaust the proxy connection pool, blocking other sites on shared infrastructure. Default mod_proxy behavior allows each child process to open max connections equal to ThreadsPerChild × ServerLimit.

▸