Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
108 lines (69 sloc) 3.26 KB

Kong Integration

Overview

The Agent's Kong check tracks total requests, response codes, client connections, and more.

Setup

Find below instructions to install and configure the check when running the Agent on a host. See the Autodiscovery Integration Templates documentation to learn how to apply those instructions to a containerized environment.

Installation

The Kong check is included in the Datadog Agent package, so you don't need to install anything else on your Kong servers.

Configuration

Edit the kong.d/conf.yaml file, in the conf.d/ folder at the root of your Agent's configuration directory.

Metric collection

Add this configuration block to your kong.d/conf.yaml file to start gathering your Kong Metrics:

```yaml
init_config:

instances:
    # Each instance needs a `kong_status_url`. Tags are optional.
    -   kong_status_url: http://example.com:8001/status/
        tags:
        - instance:foo
    #-   kong_status_url: http://example2.com:8001/status/
    #    tags:
    #    - instance:bar
```

See the sample kong.d/conf.yaml for all available configuration options.

  1. Restart the Agent to begin sending Kong metrics to Datadog.

Log Collection

Available for Agent >6.0

Kong access logs are generated by NGINX, so the default location is the same as for NGINX files.

  1. Collecting logs is disabled by default in the Datadog Agent. Enable it in datadog.yaml:

    logs_enabled: true
  2. Add this configuration block to your kong.d/conf.yaml file to start collecting your Kong Logs:

logs:
   - type: file
     path: /var/log/nginx/access.log
     service: <SERVICE>
     source: kong

   - type: file
     path: /var/log/nginx/error.log
     service: <SERVICE>
     source: kong

Change the path and service parameter values and configure them for your environment. See the sample kong.d/conf.yaml for all available configuration options.

  1. Restart the Agent.

Validation

Run the Agent's status subcommand and look for kong under the Checks section.

Data Collected

Metrics

See metadata.csv for a list of metrics provided by this integration.

Events

The Kong check does not include any events.

Service Checks

kong.can_connect:

Returns CRITICAL if the Agent cannot connect to Kong to collect metrics, otherwise OK.

Troubleshooting

Need help? Contact Datadog support.

Further Reading

You can’t perform that action at this time.