Datadog tracer (proto)


[config.trace.v3.DatadogRemoteConfig proto]

Configuration for the Remote Configuration feature.

  "polling_interval": {...}

(Duration) Frequency at which new configuration updates are queried. If no value is provided, the default value is delegated to the Datadog tracing library.


[config.trace.v3.DatadogConfig proto]

Configuration for the Datadog tracer.

This extension has the qualified name envoy.tracers.datadog


This extension is intended to be robust against untrusted downstream traffic. It assumes that the upstream is trusted.


This extension extends and can be used with the following extension category:

This extension must be configured with one of the following type URLs:

  "collector_cluster": ...,
  "service_name": ...,
  "collector_hostname": ...,
  "remote_config": {...}

(string, REQUIRED) The cluster to use for submitting traces to the Datadog agent.


(string, REQUIRED) The name used for the service when traces are generated by envoy.


(string) Optional hostname to use when sending spans to the collector_cluster. Useful for collectors that require a specific hostname. Defaults to collector_cluster above.


(config.trace.v3.DatadogRemoteConfig) Enables and configures remote configuration. Remote Configuration allows to configure the tracer from Datadog’s user interface. This feature can drastically increase the number of connections to the Datadog Agent. Each tracer regularly polls for configuration updates, and the number of tracers is the product of the number of listeners and worker threads.