> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fabricgateway.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fabricgateway.ai/_mcp/server.

# Send data plane telemetry to Honeycomb

> Send traces, metrics, and logs from an Enterprise data plane straight to Honeycomb over OTLP/gRPC.

Honeycomb accepts OTLP/gRPC, so a data plane can send its traces, metrics, and logs straight to it, without a collector. This page shows how to point the data plane at Honeycomb, keep your API key in the app Secret, and confirm that telemetry arrives.

> **Note**
>
> 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](/guides/observability/opentelemetry).

## Prerequisites

Before you begin, make sure you have the following:

* A data plane installed with the Helm chart. See [Install the data plane](/run/install).
* A Honeycomb API key that can send data.
* Egress from the gateway pods to `api.honeycomb.io` on port `443`.
* A way to add keys to the data plane's app Secret. See [Manage data plane secrets and keys](/run/secrets-and-keys).

## Point the data plane at Honeycomb

1. In your values file, turn off the chart's collector sidecar and set the Honeycomb endpoint:

   ```yaml
   otelCollector:
     enabled: false
   env:
     vars:
       OTEL_EXPORTER_OTLP_ENDPOINT: "https://api.honeycomb.io:443"
   ```

2. Add your API key to the app Secret as `OTEL_EXPORTER_OTLP_HEADERS`. For example, with the app Secret `fabric-dp-secrets` from [Install the data plane](/run/install):

   ```bash
   kubectl -n pm-fabric-dp patch secret fabric-dp-secrets --type merge \
     -p '{"stringData":{"OTEL_EXPORTER_OTLP_HEADERS":"x-honeycomb-team=YOUR_API_KEY"}}'
   ```

   If you use a Honeycomb Classic key, which sends to a named dataset, also send the dataset: `x-honeycomb-team=YOUR_API_KEY,x-honeycomb-dataset=YOUR_DATASET`.

3. Apply the change:

   ```bash
   helm upgrade fabric-dp ./fabric-gateway-chart -n pm-fabric-dp -f my-values.yaml
   ```

   If the values file didn't change, restart the gateway instead, so it reads the new Secret:

   ```bash
   kubectl -n pm-fabric-dp rollout restart deploy/fabric-gateway-chart
   ```

   With the distributed store, the gateway runs as a StatefulSet, so use `statefulset/fabric-gateway-chart` in place of `deploy/fabric-gateway-chart`.

## Confirm that telemetry arrives

1. 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](/use/authenticate).
2. In Honeycomb, look for the dataset `fabric-gateway-dp`, or the name you set in `OTEL_SERVICE_NAME`.

If nothing arrives, check the API key and egress to `api.honeycomb.io`, and check the gateway logs as shown in [Confirm that telemetry arrives](/guides/observability/opentelemetry#confirm-that-telemetry-arrives).

## Next steps

* To change sampling, service name, or message capture, see [Tune what the data plane exports](/guides/observability/opentelemetry#tune-what-the-data-plane-exports).
* To decide what to alert on, see [Monitor the data plane](/run/monitor#what-to-alert-on).