You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-web/logging-and-monitoring/prometheus.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,22 +27,22 @@ The Ingress Controller exports the following metrics:
27
27
* Exported by NGINX/NGINX Plus. Refer to the [NGINX Prometheus Exporter developer docs](https://github.com/nginxinc/nginx-prometheus-exporter#exported-metrics) to find more information about the exported metrics.
28
28
* There is a Grafana dashboard for NGINX Plus metrics located in the root repo folder.
29
29
* Calculated by the Ingress Controller:
30
-
* `controller_upstream_server_response_latency_ms_count`. Bucketed response times from when NGINX establishes a connection to an upstream server to when the last byte of the response body is received by NGINX. **Note**: The metric for the upstream isn't available until traffic is sent to the upstream. The metric isn't enabled by default. To enable the metric, set the `-enable-latency-metrics` command-line argument.
30
+
* `upstream_server_response_latency_ms_count`. Bucketed response times from when NGINX establishes a connection to an upstream server to when the last byte of the response body is received by NGINX. **Note**: The metric for the upstream isn't available until traffic is sent to the upstream. The metric isn't enabled by default. To enable the metric, set the `-enable-latency-metrics` command-line argument.
31
31
* Ingress Controller metrics
32
-
* `controller_nginx_reloads_total`. Number of successful NGINX reloads. This includes the label `reason` with 2 possible values `endpoints` (the reason for the reload was an endpoints update) and `other` (the reload was caused by something other than an endpoint update like an ingress update).
33
-
* `controller_nginx_reload_errors_total`. Number of unsuccessful NGINX reloads.
34
-
* `controller_nginx_last_reload_status`. Status of the last NGINX reload, 0 meaning down and 1 up.
35
-
* `controller_nginx_last_reload_milliseconds`. Duration in milliseconds of the last NGINX reload.
36
-
* `controller_nginx_worker_processes_total`. Number of NGINX worker processes. This metric includes the constant label `generation` with two possible values `old` (the shutting down processes of the old generations) or `current` (the processes of the current generation).
37
-
* `controller_ingress_resources_total`. Number of handled Ingress resources. This metric includes the label type, that groups the Ingress resources by their type (regular, [minion or master](/nginx-ingress-controller/configuration/ingress-resources/cross-namespace-configuration)). **Note**: The metric doesn't count minions without a master.
38
-
* `controller_virtualserver_resources_total`. Number of handled VirtualServer resources.
39
-
* `controller_virtualserverroute_resources_total`. Number of handled VirtualServerRoute resources. **Note**: The metric counts only VirtualServerRoutes that have a reference from a VirtualServer.
32
+
* `nginx_reloads_total`. Number of successful NGINX reloads. This includes the label `reason` with 2 possible values `endpoints` (the reason for the reload was an endpoints update) and `other` (the reload was caused by something other than an endpoint update like an ingress update).
33
+
* `nginx_reload_errors_total`. Number of unsuccessful NGINX reloads.
34
+
* `nginx_last_reload_status`. Status of the last NGINX reload, 0 meaning down and 1 up.
35
+
* `nginx_last_reload_milliseconds`. Duration in milliseconds of the last NGINX reload.
36
+
* `nginx_worker_processes_total`. Number of NGINX worker processes. This metric includes the constant label `generation` with two possible values `old` (the shutting down processes of the old generations) or `current` (the processes of the current generation).
37
+
* `ingress_resources_total`. Number of handled Ingress resources. This metric includes the label type, that groups the Ingress resources by their type (regular, [minion or master](/nginx-ingress-controller/configuration/ingress-resources/cross-namespace-configuration)). **Note**: The metric doesn't count minions without a master.
38
+
* `virtualserver_resources_total`. Number of handled VirtualServer resources.
39
+
* `virtualserverroute_resources_total`. Number of handled VirtualServerRoute resources. **Note**: The metric counts only VirtualServerRoutes that have a reference from a VirtualServer.
40
40
* Kubernetes Cluster metrics
41
-
* `controller_workqueue_depth` Current depth of workqueue.
42
-
* `controller_workqueue_queue_duration_second`. How long in seconds an item stays in workqueue before being requested.
43
-
* `controller_workqueue_work_duration_seconds`. How long in seconds processing an item from workqueue takes.
41
+
* `workqueue_depth` Current depth of workqueue.
42
+
* `workqueue_queue_duration_second`. How long in seconds an item stays in workqueue before being requested.
43
+
* `workqueue_work_duration_seconds`. How long in seconds processing an item from workqueue takes.
44
44
45
45
46
-
**Note**: all metrics have the namespace nginx_ingress. For example, nginx_ingress_controller_nginx_reloads_total.
46
+
**Note**: all metrics have the namespace `nginx_ingress_controller`. For example, `nginx_ingress_controller_nginx_reloads_total`.
47
47
48
48
**Note**: all metrics include the label `class`, which is set to the class of the Ingress Controller. The class is configured via the `-ingress-class` command-line argument.
0 commit comments