obsdog

Kong integration metrics

The official Datadog integration for monitoring Kong. It collects 34 metrics.

Official summary

Track total requests, response codes, client connections, and more.

Metric types

  • count (occurrences in the interval): 19
  • gauge (value at a point in time): 15

Metrics

Descriptions are the official definitions, unedited.

MetricTypeUnit
kong.bandwidth.bytes.count[OpenMetrics V2] (Kong v3+) The total bandwidth in bytes consumed per service/route in Kongcountbyte
kong.bandwidth.count[OpenMetrics V2] (Kong < 3) The total bandwidth in bytes consumed per service/route in Kongcountbyte
kong.connections_accepted[Legacy] Total number of accepted client connections.gaugeconnection
kong.connections_active[Legacy] Current number of active client connections including Waiting connections.gaugeconnection
kong.connections_handled[Legacy] Total number of handled connections. (Same as accepts unless resource limits were reached).gaugeconnection
kong.connections_reading[Legacy] Current number of connections where Kong is reading the request header.gaugeconnection
kong.connections_waiting[Legacy] Current number of idle client connections waiting for a request.gaugeconnection
kong.connections_writing[Legacy] Current number of connections where nginx is writing the response back to the client.gaugeconnection
kong.http.consumer.status.count[OpenMetrics V2] (Kong < 3) HTTP status codes for customer per service/route in Kongcountrequest
kong.http.requests.count[OpenMetrics V2] (Kong v3+) Http Status codes per service/route in Kongcountrequest
kong.http.status[OpenMetrics V2] (Kong < 3) HTTP status codes per service/route in Kongcountrequest
kong.kong.latency.ms.bucket[OpenMetrics V2] (Kong v3+) The latency of Kong specificiallycountmillisecond
kong.kong.latency.ms.count[OpenMetrics V2] (Kong v3+) The latency of Kong specificallycountmillisecond
kong.kong.latency.ms.sum[OpenMetrics V2] (Kong v3+) The latency of Kong specificallycountmillisecond
kong.latency.bucket[OpenMetrics V2] (Kong < 3) The latency added by Kong, total request time and upstream latency for each service/route in Kongcountmillisecond
kong.latency.count[OpenMetrics V2] (Kong < 3) The latency added by Kong, total request time and upstream latency for each service/route in Kongcountmillisecond
kong.latency.sum[OpenMetrics V2] (Kong < 3) The latency added by Kong, total request time and upstream latency for each service/route in Kongcountmillisecond
kong.memory.lua.shared_dict.bytes[OpenMetrics V2] The allocated slabs in bytes in a shared_dictgaugebyte
kong.memory.lua.shared_dict.total_bytes[OpenMetrics V2] The total capacity in bytes of a shared_dictgaugebyte
kong.memory.workers.lua.vms.bytes[OpenMetrics V2] The allocated bytes in worker Lua VMgaugebyte
kong.nginx.connections.total[OpenMetrics V2] (Kong v3+) The number of HTTP and stream connectionsgaugeconnection
kong.nginx.http.current_connections[OpenMetrics V2] (Kong < 3) The number of HTTP connectionsgaugeconnection
kong.nginx.requests.total[OpenMetrics V2] (Kong v3+) The number of total Nginx connectionsgaugerequest
kong.nginx.stream.current_connections[OpenMetrics V2] (Kong < 3) The number of stream connectionsgaugeconnection
kong.nginx.timers[OpenMetrics v2] (Kong v2.8+) Total number of Nginx timers in Running or Pending state.gaugeitem
kong.request.latency.ms.bucket[OpenMetrics V2] (Kong v3+) The latency added by Kong to requestscountmillisecond
kong.request.latency.ms.count[OpenMetrics V2] (Kong v3+) The latency added by Kong to requestscountmillisecond
kong.request.latency.ms.sum[OpenMetrics V2] (Kong v3+) The latency added by Kong to requestscountmillisecond
kong.session.duration.ms[OpenMetrics V2] (Kong v3+) The duration of a Kong streamcountmillisecond
kong.stream.status.count[OpenMetrics V2] The stream status codes per service/route in Kongcountrequest
kong.total_requests[Legacy] Total number of client requests.gaugerequest
kong.upstream.latency.ms.bucket[OpenMetrics V2] (Kong v3+) The upstream latency added by Kongcountmillisecond
kong.upstream.latency.ms.count[OpenMetrics V2] (Kong v3+) The upstream latency added by Kongcountmillisecond
kong.upstream.latency.ms.sum[OpenMetrics V2] (Kong v3+) The upstream latency added by Kongcountmillisecond

Official documentation

Official documentation for the Kong 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 collectionLog 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 managementDatadog AgentSoftware that runs resident on the servers and containers you monitor and delivers metrics, logs, and traces to Datadog.Foundation and data collectionMetricsFrom CPU utilization to user sign-ups, metrics are the core data of Datadog, recording every number in your environment as a time series. If you understand how they are counted before how they are collected, you avoid aggregation mistakes and unexpected charges.Foundation and data collection

Other Log Collection integrations

Kubernetes Scheduler43 metricsKubernetes14 metricsKyoto Tycoon14 metricsLighttpd30 metricsLinkerd91 metricsMapR157 metricsMap Reduce36 metricsMarathon20 metricsMarkLogic223 metricsMemcache69 metricsMesos Master73 metricsMesos Slave40 metrics