7/30/2023 0 Comments Prometheus exporterNote: The metric counts only VirtualServerRoutes that have a reference from a VirtualServer. Number of handled VirtualServerRoute resources. controller_virtualserverroute_resources_total.Number of handled VirtualServer resources. controller_virtualserver_resources_total.Note: The metric doesn’t count minions without a master. This metric includes the label type, that groups the Ingress resources by their type (regular, minion or master). 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). controller_nginx_worker_processes_total.Duration in milliseconds of the last NGINX reload. controller_nginx_last_reload_milliseconds.Status of the last NGINX reload, 0 meaning down and 1 up. 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). To enable the metric, set the -enable-latency-metrics command-line argument. Note: The metric for the upstream isn’t available until traffic is sent to the upstream. 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. controller_upstream_server_response_latency_ms_count.There is a Grafana dashboard for NGINX Plus metrics located in the root repo folder.Refer to the NGINX Prometheus Exporter developer docs to find more information about the exported metrics. The Ingress Controller exports the following metrics: If you’re using Helm to install the Ingress Controller, to enable Prometheus metrics, configure the prometheus.* parameters of the Helm chart. Add the Prometheus port to the list of the ports of the Ingress Controller container in the template of the Ingress Controller pod:Īnnotations : prometheus.io/scrape : "true" prometheus.io/port : "9113" prometheus.io/scheme : http.To enable TLS for the Prometheus endpoint, configure the -prometheus-tls-secret cli argument with the namespace and name of a TLS Secret.As a result, the Ingress Controller will expose NGINX or NGINX Plus metrics in the Prometheus format via the path /metrics on port 9113 (customizable via the -prometheus-metrics-listen-port command-line argument). Run the Ingress Controller with the -enable-prometheus-metrics command-line argument.If you’re using Kubernetes manifests (Deployment or DaemonSet) to install the Ingress Controller, to enable Prometheus metrics: Those include NGINX/NGINX Plus and the Ingress Controller metrics. The Ingress Controller exposes a number of metrics in the Prometheus format. NGINX Ingress Controller and Open Service Mesh.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |