AI BriefingIngress-Nginx v1.12.0 Excludes Deprecated upstreamLatency Metric from Default Collection
Key point
Starting with Ingress-Nginx Controller v1.12.0, the upstreamLatency metric, a primary source of performance degradation, is excluded from default collection to alleviate bottlenecks in high-traffic environments.
Details
Ingress-Nginx Controller has experienced bottlenecks where multiple Goroutines were blocked waiting for Mutex Locks when collecting metrics from Nginx Workers as Prometheus Summary types. In particular, the Summary type upstreamLatency metric had slow storage speeds and was a primary cause of performance degradation in high-traffic environments. Previously, the --exclude-socket-metrics flag had to be manually configured, but starting with version v1.12.0 released in late December 2024, this metric is excluded from default collection, allowing these bottlenecks to be resolved without manual intervention.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.
Related
LLM Serving: The Difference Between Launching and Launching Well
KT Cloud Aims to Cut Deployment Failure Root Cause Analysis Time by 90% Using MCPKT Cloud Proposes Three Architectural Boundaries for Heterogeneous Data Integration