Monitoring NGINX Ingress Controller (deprecated) (FREE)
Deprecated in GitLab 14.7.
WARNING: This feature is in its end-of-life process. It is deprecated in GitLab 14.7, and is planned for removal in GitLab 16.0.
GitLab has support for automatically detecting and monitoring the Kubernetes NGINX Ingress controller. This is provided by leveraging the built-in Prometheus metrics included with Kubernetes NGINX Ingress controller version 0.16.0 onward.
NOTE: NGINX Ingress versions prior to 0.16.0 offer an included VTS Prometheus metrics exporter, which exports metrics different than the built-in metrics.
Prometheus integration must be active.
|HTTP Error Rate (%)||
Configuring NGINX Ingress monitoring
Version 0.9.0 and above of NGINX Ingress have built-in support for exporting Prometheus metrics. To enable, a ConfigMap setting must be passed:
enable-vts-status: "true". Once enabled, a Prometheus metrics endpoint starts running on port 10254.
Next, the Ingress needs to be annotated for Prometheus monitoring. Two new annotations need to be added:
Managing these settings depends on how NGINX Ingress has been deployed. If you have deployed via the official Helm chart, metrics can be enabled with
controller.stats.enabled along with the required annotations. Alternatively it is possible to edit the NGINX Ingress YAML directly in the Kubernetes dashboard.
Specifying the Environment label
To isolate and display only relevant metrics for a given environment, GitLab needs a method to
detect which labels are associated. To do this, GitLab searches for metrics with appropriate labels.
In this case, the
ingress label must include the value
If you have used Auto Deploy to deploy your app, this format is used automatically and metrics are detected with no action on your part.