obsdog

nginx-ingress-controller integration metrics

The official Datadog integration for monitoring nginx-ingress-controller. It collects 30 metrics.

Official summary

Monitor metrics about the NGINX ingress controller and the embedded NGINX.

Metric types

  • gauge (value at a point in time): 22
  • count (occurrences in the interval): 8

Metrics

Descriptions are the official definitions, unedited.

MetricTypeUnit
nginx_ingress.controller.connect.duration.countCount of upstream connection time per Ingressgauge-
nginx_ingress.controller.connect.duration.sumSum of upstream connection time per Ingressgaugesecond
nginx_ingress.controller.cpu.timeCpu usage in secondscountsecond
nginx_ingress.controller.header.duration.countCount of time to receive the response header from the upstream server per Ingressgauge-
nginx_ingress.controller.header.duration.sumSum of time to receive the response header from the upstream server per Ingressgaugesecond
nginx_ingress.controller.last.reload.successWhether the last configuration reload attempt was successfulgauge-
nginx_ingress.controller.mem.residentResident memory size in bytesgaugebyte
nginx_ingress.controller.mem.virtualVirtual memory size in bytesgaugebyte
nginx_ingress.controller.reload.successCumulative number of Ingress controller reload operationscount-
nginx_ingress.controller.request.duration.countThe count of request processing timegauge-
nginx_ingress.controller.request.duration.sumThe sum of request processing timegaugemillisecond
nginx_ingress.controller.request.size.countThe count of request sizegauge-
nginx_ingress.controller.request.size.sumThe sum of request sizegaugebyte
nginx_ingress.controller.requestsThe total number of client requestscountrequest
nginx_ingress.controller.response.duration.countCount of response duration per Ingressgauge-
nginx_ingress.controller.response.duration.sumSum of response duration per Ingressgaugesecond
nginx_ingress.controller.response.size.countCount of response size per Ingressgauge-
nginx_ingress.controller.response.size.sumSum of response size per Ingressgaugebyte
nginx_ingress.controller.upstream.latency.count[Deprecated] Count of upstream service latency per Ingressgauge-
nginx_ingress.controller.upstream.latency.quantile[Deprecated] Quantiles of upstream service latency per Ingressgaugesecond
nginx_ingress.controller.upstream.latency.sum[Deprecated] Sum of upstream service latency per Ingressgaugesecond
nginx_ingress.nginx.bytes.readNumber of bytes readcountbyte
nginx_ingress.nginx.bytes.writeNumber of bytes writtencountbyte
nginx_ingress.nginx.connections.currentCurrent number of client connections with stategaugeconnection
nginx_ingress.nginx.connections.totalTotal number of connections with statecountconnection
nginx_ingress.nginx.cpu.timeCpu usage in secondscountsecond
nginx_ingress.nginx.mem.residentResident memory size in bytesgaugebyte
nginx_ingress.nginx.mem.virtualVirtual memory size in bytesgaugebyte
nginx_ingress.nginx.process.countNumber of nginx processesgaugeprocess
nginx_ingress.nginx.requests.totalTotal number of client requestscountrequest

Official documentation

Official documentation for the nginx-ingress-controller integration

Metric names and descriptions are the official Datadog integration definitions (Copyright Datadog, Inc., BSD-3-Clause), reproduced unedited. The full license terms are on the About page.

Related products

IntegrationsIntegrations are the bundle of entry points that pour data from external systems such as AWS and MySQL into Datadog. Where you configure them splits into two families, the Agent side and the cloud account side, and which one you choose changes both what you can see and how billing is counted.Foundation and data collectionContainer MonitoringA mechanism for following containers that are born and gone within seconds and keep moving between nodes, with the same hands-on approach as host monitoring. On Kubernetes, how the Agent is placed and how billing is counted are both specific to containers, so we cover those two points first.Infrastructure monitoringLog ManagementLog Management is the product that gathers logs from servers, containers, and cloud services in one place and connects them to search, retention, and notification. It has a distinctive structure in which ingestion and indexing are billed separately.Log managementNetwork MonitoringA group of features for finding failures that happen not inside a server but "between servers." With two pillars, CNM, which follows traffic flows on the cloud side, and NDM, which watches routers and switches via SNMP, it fills the blind spot of host monitoring.Infrastructure monitoring

Other Orchestration integrations

Oracle Container Engine for Kubernetes5 metricsOpenShift43 metricsOpenStack Controller276 metricsZooKeeper268 metricsConsul152 metricsAmazon ECS on AWS Fargate34 metricsetcd196 metricsKubernetes Controller Manager28 metricsKubernetes Metrics Server15 metricsKubernetes Scheduler43 metricsKubernetes14 metricsKubernetes State118 metrics