datadog/envoy-apm-experimental repository overview

⁠DEPRECATED

⁠Envoy image with Datadog APM support

Note: This feature has now been merged into envoy. The configuration instructions can be used with the envoyproxy/envoy:latest image.

⁠Configuration

To enable datadog tracing, the following items need to be added to the envoy configuration.

• an additional "cluster" refers to the datadog agent on the host running envoy.

  clusters:
  ... existing cluster configs ...
  - name: datadog_agent
    connect_timeout: 1s
    type: strict_dns
    lb_policy: round_robin
    hosts:
    - socket_address:
        address: AGENT-ADDRESS
        port_value: 8126

The value for AGENT-ADDRESS needs to be replaced with an address that envoy can connect to for the local agent.

• tracing configuration using envoy.tracers.datadog

tracing:
  http:
    name: envoy.tracers.datadog
    config:
      collector_cluster: datadog_agent
      service_name: envoy-frontend

The value for collector_cluster must match the name used in the first section. The service_name can be replaced with a meaningful value.

• tracing configuration in http_connection_manager

      - name: envoy.http_connection_manager
        config:
          tracing:
            operation_name: egress

These config snippets are similar to the ones used by other tracers, and this example can be used as a guide for placement: https://github.com/envoyproxy/envoy/blob/master/examples/jaeger-tracing/front-envoy-jaeger.yaml#L41-L53⁠ https://github.com/envoyproxy/envoy/blob/master/examples/jaeger-tracing/front-envoy-jaeger.yaml#L11-L12⁠