.. _envoy_v3_api_file_envoy/config/trace/v3/datadog.proto: Datadog tracer ============== This documentation is for the Envoy v3 API. As of Envoy v1.18 the v2 API has been removed and is no longer supported. If you are upgrading from v2 API config you may wish to view the v2 API documentation: :ref:`config/trace/v2/datadog.proto ` .. _envoy_v3_api_msg_config.trace.v3.DatadogConfig: config.trace.v3.DatadogConfig ----------------------------- :repo:`[config.trace.v3.DatadogConfig proto] ` Configuration for the Datadog tracer. .. _extension_envoy.tracers.datadog: This extension may be referenced by the qualified name ``envoy.tracers.datadog`` .. note:: This extension is intended to be robust against untrusted downstream traffic. It assumes that the upstream is trusted. .. tip:: This extension extends and can be used with the following extension category: - :ref:`envoy.tracers ` .. code-block:: json { "collector_cluster": "...", "service_name": "..." } .. _envoy_v3_api_field_config.trace.v3.DatadogConfig.collector_cluster: collector_cluster (`string `_, *REQUIRED*) The cluster to use for submitting traces to the Datadog agent. .. _envoy_v3_api_field_config.trace.v3.DatadogConfig.service_name: service_name (`string `_, *REQUIRED*) The name used for the service when traces are generated by envoy.