Technologies/Envoy/envoy.cluster.upstream.connection.active
EnvoyEnvoyMetric

envoy.cluster.upstream.connection.active

Active upstream connections
Dimensions:None
Available on:PrometheusPrometheus (1)OpenTelemetryOpenTelemetry (1)Native (1)
Interface Metrics (3)
PrometheusPrometheus
Current number of active upstream connections to cluster members
Dimensions:None
OpenTelemetryOpenTelemetry
Current number of active connections to upstream cluster members
Dimensions:None
Native
Current number of active connections to upstream cluster members
Dimensions:None
Sources
envoy_cluster_upstream_cx_activewww.envoyproxy.io
envoy.cluster.upstream.connection.activegithub.com
cluster.upstream_cx_activewww.envoyproxy.io

Technical Annotations (7)

Configuration Parameters (1)
nofile
OS ulimit for max open files per process; increase from default when handling high connection volumes
Error Signatures (2)
139exit code
Caught Segmentation fault, suspect faulting address 0x0log pattern
CLI Commands (2)
kubectl exec deploy/my-service -c istio-proxy -- pilot-agent request GET stats | grep "downstream_cx_active\|upstream_cx_active"diagnostic
kubectl exec deploy/my-service -c istio-proxy -- pilot-agent request GET stats | grep "downstream_cx_total\|upstream_cx_total"diagnostic
Technical References (2)
nofile ulimitconfigurationUlimit settingsconfiguration
Related Insights (3)
High active connection count indicates connection leakswarning
▸
Active connection spikes indicate load balancer misconfigurationwarning
▸
Envoy segfault crash due to file descriptor limit under high loadcritical
▸