Send data plane telemetry to Grafana Cloud
Grafana Cloud’s OTLP endpoint accepts OTLP over HTTP only, and the gateway exports over gRPC, so the gateway can’t send to it directly. Instead, you replace the chart’s collector sidecar with one that receives the gateway’s OTLP/gRPC on localhost:4317 and re-exports it to Grafana Cloud over HTTP. This page shows how to set up that sidecar, keep your Grafana Cloud credentials in the app Secret, 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.
- Your Grafana Cloud stack’s OTLP endpoint, instance ID, and an access token that can write telemetry.
- Egress from the gateway pods to your Grafana Cloud OTLP endpoint.
- A way to add keys to the data plane’s app Secret. See Manage data plane secrets and keys.
Add your credentials to the app Secret
The sidecar authenticates with HTTP Basic auth. Add the base64 encoding of <instance-id>:<token> to the app Secret as GRAFANA_CLOUD_AUTH:
tr -d '\n' removes the line breaks that base64 adds to long output on Linux, which would make the patch invalid JSON. Replace fabric-dp-secrets with the name of your app Secret, the one in secrets.app.existingSecret. If you manage the Secret through a secret manager, add the key there instead.
Replace the collector sidecar
-
In your values file, replace the chart’s sidecar with this one. Set the endpoint to your stack’s region, and keep
otelCollector.enabledat its default oftrue. Setting it tofalseremoves any sidecar namedotel-collector, including this one:The chart fills in the app Secret’s name for
{{ include "appSecretName" $ }}, so you don’t need to change it. LeaveOTEL_EXPORTER_OTLP_ENDPOINTat the chart’s default,http://localhost:4317, so the gateway sends to this sidecar. If you mirror images, mirror the collector image too and changeimage. -
Apply the change:
This sidecar forwards only what the gateway sends. It doesn’t scrape the collector’s or the embedder’s metrics, and it doesn’t drop health-check traces or apply the default sidecar’s trace filtering. Add those to its configuration if you need them.
Confirm that telemetry arrives
-
Check that the gateway pods are
READY 2/2: -
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 Grafana Cloud, search your traces for the service
fabric-gateway-dp, or the name you set inOTEL_SERVICE_NAME.
If nothing arrives, check the sidecar’s logs for export errors:
With the distributed store, use statefulset/fabric-gateway-chart in place of deploy/fabric-gateway-chart.
An authentication error usually means GRAFANA_CLOUD_AUTH isn’t the base64 encoding of <instance-id>:<token>.
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.

