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 0.11.0 differs from what is documented herein. Refer to the CHANGELOG for details.

Terminology

  • 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: an entity that makes requests for Kong to proxy; it represents either a user or an external service.
  • 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.

Configuration

This plugin is compatible with requests with the following protocols:

  • http
  • https

This plugin is compatible with DB-less mode.

Enabling the plugin on a Service

With a database

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=127.0.0.1" \
    --data "config.port=8125"

Without a database

Configure this plugin on a Service by adding this section do 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

With a database

Configure this plugin on a Route with:

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

Without a database

Configure this plugin on a Route by adding this section do 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

With a database

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

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

Without a database

Configure this plugin on a Consumer by adding this section do 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.

You can combine consumer.id and service.id in the same request, to furthermore narrow the scope of the plugin.

Global plugins

  • Using a database, all plugins can be configured using the http://kong:8001/plugins/ endpoint.
  • Without a database, all plugins can be configured via the plugins: entry on the declarative configuration file.

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.

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 following metrics to the Datadog server about a Service or Route.

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