The Service Map for APM is here!

Tracing Docker Applications

Enable the datadog-trace-agent in the datadog/agent container by passing DD_APM_ENABLED=true as an environment variable.

List of all environment variables available:

Environment variable Description
DD_API_KEY Datadog API Key
DD_APM_ENABLED When set to true, the Datadog Agent accepts trace metrics.
DD_APM_DD_URL Datadog API endpoint where traces are sent.
DD_PROXY_HTTPS Set up the URL for the proxy to use.
DD_HOSTNAME Set manually the Agent hostname.
DD_BIND_HOST Set the StatsD & receiver hostname.
DD_RECEIVER_PORT Port that the Datadog Agent’s trace receiver listen on. Default value is 8126.
DD_DOGSTATSD_PORT Set the DogStatsD port.
DD_APM_NON_LOCAL_TRAFFIC Allow non-local traffic when tracing from other containers.
DD_IGNORE_RESOURCE A comma-separated list of resources that the Agent should ignore.
DD_LOG_LEVEL Set the logging level. (trace/debug/info/warn/error/critical/off)
DD_APM_ANALYZED_SPANS Configure the spans to analyze for transactions.

Tracing from the host

Tracing is available on port 8126/tcp from any host by adding the option -p 8126:8126/tcp to the docker run command.

To make it available from your host only, use -p instead.

For example, the following command allows the Agent to receive traces from anywhere:

docker run -d -v /var/run/docker.sock:/var/run/docker.sock:ro \
              -v /proc/:/host/proc/:ro \
              -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
              -e DD_API_KEY=<YOUR_API_KEY> \
              -e DD_APM_ENABLED=true \

Tracing from other containers

As with DogStatsD, traces can be submitted to the Agent from other containers either using Docker networks or with the Docker host IP.

Docker Network

As a first step, create a user-defined bridge network:

docker network create <NETWORK_NAME>

Then start the Agent and the application container, connected to the network previously created:

# Datadog Agent
docker run -d --name datadog-agent \
              --network <NETWORK_NAME> \
              -v /var/run/docker.sock:/var/run/docker.sock:ro \
              -v /proc/:/host/proc/:ro \
              -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
              -e DD_API_KEY=<YOUR_API_KEY> \
              -e DD_APM_ENABLED=true \
              -e DD_APM_NON_LOCAL_TRAFFIC=true \

# Application
docker run -d --name app \
              --network <NETWORK_NAME> \

This exposes the hostname datadog-agent in your app container. If you’re using docker-compose, <NETWORK_NAME> parameters are the ones defined under the networks section of your docker-compose.yml.

Your application tracers must be configured to submit traces to this address. See the examples below for each supported language:

Either update the Java Agent configuration via environment variables:

DD_AGENT_HOST=datadog-agent \
java -javaagent:/path/to/the/dd-java-agent.jar -jar /your/app.jar

or via system properties:

java -javaagent:/path/to/the/dd-java-agent.jar \ \
     -Ddd.agent.port=8126 \
     -jar /your/app.jar
from ddtrace import tracer

Datadog.configure do |c|
  c.tracer hostname: 'datadog-agent',
           port: 8126
package main

import ""

func main() {
    defer tracer.Stop()
const tracer = require('dd-trace').init({
  hostname: 'datadog-agent',
  port: 8126

Docker host IP

Agent container port 8126 should be linked to the host directly. Configure your application tracer to report to the default route of this container (determine this using the ip route command).

The following is an example for the Python Tracer, assuming is the default route:

from ddtrace import tracer

tracer.configure(hostname='', port=8126)

Further Reading

Additional helpful documentation, links, and articles: