Export telemetry with OpenTelemetry
A data plane emits traces, metrics, and logs over OTLP/gRPC, so you can send them to any OpenTelemetry backend. It exports only to destinations that you configure. This page shows the two ways to route that telemetry, how to point the data plane at an OTLP endpoint, how to tune or turn off export, and how to confirm that telemetry arrives.
This applies to the Enterprise plan, where the data plane runs in your VPC. On the Free plan, Postman runs the data plane, and you review traffic in the console instead. For more information, see Monitor gateway traffic.
Choose how telemetry leaves the pod
The gateway always sends OTLP/gRPC to OTEL_EXPORTER_OTLP_ENDPOINT. What sits at that address is up to you:
With the direct approach, the sidecar’s extra processing goes away: you receive every sampled trace, and the collector and embedder metrics aren’t shipped. For the sidecar’s details, see Monitor the data plane.
Usage metering travels to the control plane on the data plane’s own connection, so nothing on this page affects billing or usage data.
Prerequisites
Before you begin, make sure you have the following:
- A data plane installed with the Helm chart. For the steps, see Install the data plane.
- An OTLP/gRPC endpoint that the gateway pods can reach, and any credentials that your backend needs.
- A way to add keys to the data plane’s app Secret. See Manage data plane secrets and keys.
Send telemetry straight to an OTLP endpoint
-
In your values file, turn off the collector sidecar and set your endpoint:
Use an
https://endpoint for a backend that needs TLS. -
If your backend needs an API key or other headers, add
OTEL_EXPORTER_OTLP_HEADERSto the app Secret rather than to the values file. The value is a comma-separated list ofname=valuepairs. A key in the app Secret overrides the same key inenv.vars. For example, with the app Secretfabric-dp-secretsfrom Install the data plane:If you manage the Secret through a secret manager, add the key there instead.
-
Apply the change:
If you changed only the Secret, restart the gateway so it reads the new value:
With the distributed store, the gateway runs as a StatefulSet, so use
statefulset/fabric-gateway-chartin place ofdeploy/fabric-gateway-chart.
If you turn off the sidecar without changing OTEL_EXPORTER_OTLP_ENDPOINT, the gateway still sends to localhost:4317, and the telemetry is dropped.
The chart’s own examples drop the sidecar with additionalContainers: [] instead. That also works, but it removes any other sidecar you added to that list, so prefer otelCollector.enabled: false.
Tune what the data plane exports
The gateway reads the standard OpenTelemetry variables. Set them under env.vars in your values file:
Captured message content can contain prompts and personal data. When the PII Redaction plugin runs on a request, the exported content is the scrubbed version. Otherwise it’s exported as sent. Turn capture on only if your data-handling rules allow it.
Turn off telemetry export
To export nothing, turn off the sidecar and every signal:
The gateway still reads and passes on trace context, so traces your own services start stay connected across the gateway. Logs still go to standard output.
Confirm that telemetry arrives
- Send a request through a route on the data plane. For the steps, see Authenticate and send a request.
- In your backend, search for traces from the service
fabric-gateway-dp, or the name that you set inOTEL_SERVICE_NAME. The chart samples 10% of new traces, so send several requests.
If nothing arrives, check the gateway logs:
With the distributed store, use statefulset/fabric-gateway-chart in place of deploy/fabric-gateway-chart.
A warning that tracing, metrics, or logs are enabled but no endpoint is configured means the gateway found no OTLP endpoint for that signal. If you kept the sidecar, check its export failures, as shown in Monitor the data plane.
Next steps
- To set up a specific backend, see Datadog, Grafana Cloud, Honeycomb, or New Relic.
- To review the data plane’s health and metrics, see Monitor the data plane.

