Log metrics for a Service, Route (or the deprecated API entity) to a local Datadog agent.

Note: The functionality of this plugin as bundled with versions of Kong prior to 0.11.0 differs from what is documented herein. Refer to the CHANGELOG for details.


  • plugin: a plugin executing actions inside Kong before or after a request has been proxied to the upstream API.
  • Service: the Kong entity representing an external upstream API or microservice.
  • Route: the Kong entity representing a way to map downstream requests to upstream services.
  • Consumer: the Kong entity representing a developer or machine using the API. When using Kong, a Consumer only communicates with Kong which proxies every call to the said upstream API.
  • Credential: a unique string associated with a Consumer, also referred to as an API key.
  • upstream service: this refers to your own API/service sitting behind Kong, to which client requests are forwarded.
  • API: a legacy entity used to represent your upstream services. Deprecated in favor of Services since CE 0.13.0 and EE 0.32.


Enabling the plugin on a Service

Configure this plugin on a Service by making the following request:

$ curl -X POST http://kong:8001/services/{service}/plugins \
    --data "name=datadog"  \
    --data "config.host=" \
    --data "config.port=8125"

  • service: the id or name of the Service that this plugin configuration will target.

Enabling the plugin on a Route

Configure this plugin on a Route with:

$ curl -X POST http://kong:8001/routes/{route_id}/plugins \
    --data "name=datadog"  \
    --data "config.host=" \
    --data "config.port=8125"

  • route_id: the id of the Route that this plugin configuration will target.

Enabling the plugin on a Consumer

You can use the http://localhost:8001/plugins endpoint to enable this plugin on specific Consumers:

$ curl -X POST http://kong:8001/plugins \
    --data "name=datadog" \
    --data "consumer_id={consumer_id}"  \
    --data "config.host=" \
    --data "config.port=8125"

Where consumer_id is the id of the Consumer we want to associate with this plugin.

You can combine consumer_id and service_id

in the same request, to furthermore narrow the scope of the plugin.

Enabling the plugin on an API

If you are using an older version of Kong with the legacy API entity (deprecated in favor of Services since CE 0.13.0 and EE 0.32.), you can configure this plugin on top of such an API by making the following request:

$ curl -X POST http://kong:8001/apis/{api}/plugins \
    --data "name=datadog"  \
    --data "config.host=" \
    --data "config.port=8125"

  • api: either id or name of the API that this plugin configuration will target.

Global plugins

All plugins can be configured using the http://kong:8001/plugins/ endpoint. A plugin which is not associated to any Service, Route or Consumer (or API, if you are using an older version of Kong) is considered "global", and will be run on every request. Read the Plugin Reference and the Plugin Precedence sections for more information.


Here's a list of all the parameters which can be used in this plugin's configuration:

form parameterdefaultdescription
nameThe name of the plugin to use, in this case datadog
service_idThe id of the Service which this plugin will target.
route_idThe id of the Route which this plugin will target.
enabledtrueWhether this plugin will be applied.
consumer_idThe id of the Consumer which this plugin will target.
api_idThe id of the API which this plugin will target. Note: The API Entity is deprecated in favor of Services since CE 0.13.0 and EE 0.32.

The IP address or host name to send data to.



The port to send data to on the upstream server


All metrics are logged

List of Metrics to be logged. Available values are described at Metrics.



String to be attached as prefix to metric’s name.


Plugin currently logs following metrics to the Datadog server about a Service, Route, or an API entity (which is deprecated since 0.13.0).

Metric description namespace
request_count tracks the request kong.<api_name>.request.count
request_size tracks the request’s body size in bytes kong.<api_name>.request.size
response_size tracks the response’s body size in bytes kong.<api_name>.response.size
latency tracks the time interval between the request started and response received from the upstream server kong.<api_name>.latency
status_count tracks each status code returned as response kong.<api_name>.status.<status>.count and kong.<api_name>.status.<status>.total
unique_users tracks unique users made a request to the api kong.<api_name>.user.uniques
request_per_user tracks request/user kong.<api_name>.user.<consumer_id>.count
upstream_latency tracks the time it took for the final service to process the request kong.<api_name>.upstream_latency
kong_latency tracks the internal Kong latency that it took to run all the plugins kong.<api_name>.kong_latency
status_count_per_user tracks request/status/user kong.<api_name>.user.<customer_id>.status.<status> and kong.<api_name>.user.<customer_id>.status.total

Metric fields

Plugin can be configured with any combination of Metrics, with each entry containing the following fields.

Field description allowed values
name Datadog metric’s name Metrics
stat_type determines what sort of event the metric represents gauge, timer, counter, histogram, meter and set
sampling rate number
authenticated user detail consumer_id, custom_id, username
List of tags key[:value]

Metric requirements

  1. by default all metrics get logged.
  2. metric with stat_type as counter or gauge must have sample_rate defined as well.
  3. unique_users metric only works with stat_type as set.
  4. status_count, status_count_per_user and request_per_user work only with stat_type as counter.
  5. status_count_per_user, request_per_user and unique_users must have customer_identifier defined.

Kong Process Errors

This logging plugin will only log HTTP request and response data. If you are looking for the Kong process error file (which is the nginx error file), then you can find it at the following path: {prefix}/logs/error.log