Send data plane telemetry to Datadog
You can send a data plane’s traces, metrics, and logs to Datadog through a Datadog Agent that accepts OTLP/gRPC. The gateway sends straight to the Agent, and the Agent holds your Datadog API key, so the data plane needs no Datadog credentials. This page shows how to point the data plane at the Agent and confirm that telemetry arrives.
This applies to the Enterprise plan, where the data plane runs in your VPC. For how data plane telemetry export works in general, see Export telemetry with OpenTelemetry.
Prerequisites
Before you begin, make sure you have the following:
- A data plane installed with the Helm chart. See Install the data plane.
- A Datadog Agent with OTLP ingestion over gRPC turned on, listening on port
4317, and reachable from the gateway pods. See Datadog’s documentation for the Agent’s OTLP settings.
Point the data plane at the Agent
-
In your values file, turn off the chart’s collector sidecar and set the Agent as the endpoint:
Replace
<datadog-agent-host>with the Agent’s address, for example its Kubernetes Service name. -
Apply the change:
Confirm that telemetry arrives
- Send several requests through a route on the data plane. The chart samples 10% of new traces. For the steps, see Authenticate and send a request.
- In Datadog, search APM for the service
fabric-gateway-dp, or the name you set inOTEL_SERVICE_NAME.
If nothing arrives, check that the gateway pods can reach the Agent on port 4317, and check the gateway logs as shown in Confirm that telemetry arrives.
Next steps
- To change sampling, service name, or message capture, see Tune what the data plane exports.
- To decide what to alert on, see Monitor the data plane.

