How to keep Ingress NGINX Controller metric volumes manageable and still meaningful
The Ingress NGINX Controller is a widely used Kubernetes component for managing HTTP and HTTPS traffic routing. While it provides powerful observability through Prometheus metrics, it’s also notorious for generating an excessively high number of time series. The root cause lies in how the controller labels its metrics—tracking requests across multiple dimensions such as ingress name, host, path, status code, and upstream response times.