In order to give you better service we use cookies. By continuing to use our website, you agree to the use of cookies as described in our Cookie Policy

Kong Logo
header icon

Datadog

Log metrics for a Service, Route to a local Datadog agent.

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

Configuration Reference

You can configure this plugin using the Kong Admin API or through declarative configuration, which involves directly editing the Kong configuration file.

This plugin is compatible with requests with the following protocols:

  • http
  • https

This plugin is compatible with DB-less mode.

In DB-less mode, Kong does not have an Admin API. If using this mode, configure the plugin using declarative configuration.

Enabling the plugin on a Service

Kong Admin API
Kubernetes
Declarative (YAML)

For example, configure this plugin on a Service by making the following request:

$ curl -X POST http://<admin-hostname>:8001/services/<service>/plugins \
    --data "name=datadog"  \
    --data "config.host=127.0.0.1" \
    --data "config.port=8125"

First, create a KongPlugin resource:

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: <datadog-example>
config: 
  host: 127.0.0.1
  port: 8125
plugin: datadog

Next, apply the KongPlugin resource to a Service by annotating the Service as follows:

apiVersion: v1
kind: Service
metadata:
  name: <service>
  labels:
    app: <service>
  annotations:
    plugins.konghq.com: <datadog-example>
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
    name: <service>
  selector:
    app: <service>
Note: The KongPlugin resource only needs to be defined once and can be applied to any Service, Consumer, or Route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

For example, configure this plugin on a Service by adding this section to your declarative configuration file:

plugins:
- name: datadog
  service: <service>
  config: 
    host: 127.0.0.1
    port: 8125

<service> is the id or name of the Service that this plugin configuration will target.

Enabling the plugin on a Route

Kong Admin API
Kubernetes
Declarative (YAML)

For example, configure this plugin on a Route with:

$ curl -X POST http://<admin-hostname>:8001/routes/<route>/plugins \
    --data "name=datadog"  \
    --data "config.host=127.0.0.1" \
    --data "config.port=8125"

First, create a KongPlugin resource:

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: <datadog-example>
config: 
  host: 127.0.0.1
  port: 8125
plugin: datadog

Then, apply it to an ingress (Route or Routes) by annotating the ingress as follows:

apiVersion: networking/v1beta1
kind: Ingress
metadata:
  name: <route>
  annotations:
    plugins.konghq.com: <datadog-example>
spec:
  rules:
  - host: examplehostname.com
    http:
      paths:
      - path: /bar
        backend:
          serviceName: echo
          servicePort: 80
Note: The KongPlugin resource only needs to be defined once and can be applied to any Service, Consumer, or Route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

For example, configure this plugin on a Route by adding this section to your declarative configuration file:

plugins:
- name: datadog
  route: <route>
  config: 
    host: 127.0.0.1
    port: 8125

<route> is the id or name of the Route that this plugin configuration will target.

Enabling the plugin on a Consumer

Kong Admin API
Kubernetes
Declarative (YAML)

For example, configure this plugin on a Consumer with:

$ curl -X POST http://<admin-hostname>:8001/consumers/<consumer>/plugins \
    --data "name=datadog"  \
    --data "config.host=127.0.0.1" \
    --data "config.port=8125"

You can combine consumer.id, service.id, or route.id in the same request, to further narrow the scope of the plugin.

First, create a KongPlugin resource:

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: <datadog-example>
config: 
  host: 127.0.0.1
  port: 8125
plugin: datadog

Then, apply it to a Consumer by annotating the KongConsumer resource as follows:

apiVersion: configuration.konghq.com/v1
kind: KongConsumer
metadata:
  name: <consumer>
  annotations:
    plugins.konghq.com: <datadog-example>
Note: The KongPlugin resource only needs to be defined once and can be applied to any Service, Consumer, or Route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

For example, configure this plugin on a Consumer by adding this section to your declarative configuration file:

plugins:
- name: datadog
  consumer: <consumer>
  config: 
    host: 127.0.0.1
    port: 8125

<consumer> is the id or username of the Consumer that this plugin configuration will target.

Enabling the plugin globally

A plugin which is not associated to any Service, Route, or Consumer is considered global, and will be run on every request. Read the Plugin Reference and the Plugin Precedence sections for more information.

Kong Admin API
Kubernetes
Declarative (YAML)

For example, configure this plugin globally with:

$ curl -X POST http://<admin-hostname>:8001/plugins/ \
    --data "name=datadog"  \
    --data "config.host=127.0.0.1" \
    --data "config.port=8125"

Create a KongClusterPlugin resource and label it as global:

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: <global-datadog>
  labels:
    global: \"true\"
config: 
  host: 127.0.0.1
  port: 8125
plugin: datadog

For example, configure this plugin using the plugins: entry in the declarative configuration file:

plugins:
- name: datadog
  config: 
    host: 127.0.0.1
    port: 8125

Parameters

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

Form ParameterDescription
nameThe name of the plugin to use, in this case datadog.
service.idThe ID of the Service the plugin targets.
route.idThe ID of the Route the plugin targets.
consumer.idThe ID of the Consumer the plugin targets.
enabled

default value: true		Whether this plugin will be applied.
config.host
optional

default value:

127.0.0.1

The IP address or host name to send data to.
config.port
optional

default value:

8125

The port to send data to on the upstream server
config.metrics
optional

default value:

All metrics are logged

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

default value:

kong

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

Metrics

Plugin currently logs the following metrics to the Datadog server about a Service or Route.

Metric description namespace
request_count tracks the request kong.request.count
request_size tracks the request’s body size in bytes kong.request.size
response_size tracks the response’s body size in bytes kong.response.size
latency tracks the time interval between the request started and response received from the upstream server kong.latency
upstream_latency tracks the time it took for the final service to process the request kong.upstream_latency
kong_latency tracks the internal Kong latency that it took to run all the plugins kong.kong_latency

The metrics will be sent with the tags name and status carrying the API name and HTTP status code respectively. If you specify consumer_identifier with the metric, a tag consumer will be added.

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
sample_rate
conditional		 sampling rate number
customer_identifier
conditional		 authenticated user detail consumer_id, custom_id, username
tags
optional		 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.

Migrating Datadog queries

The plugin updates replace the api, status, and consumer-specific metrics with a generic metric name. You have to change your Datadog queries in dashboards and alerts to reflect the metrics updates.

For example, the following query:

avg:kong.sample_service.latency.avg{*}

would need to change to:

avg:kong.latency.avg{name:sample-service}

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