Skip to main content
e6data exposes its operational telemetry via OpenTelemetry so you can route metrics, logs, and traces into your own observability platform (Datadog, Honeycomb, Grafana, New Relic, and so on).

​
What’s exposed

All three follow the OpenTelemetry standard, so any OTLP-compatible backend can ingest them.

​
Configure OTel export

In the Compute Plane, go to Settings → Observability:
  1. Enable Export to OpenTelemetry.
  2. Set the OTLP endpoint for your backend (HTTPS, typically port 443 or 4318).
  3. Set the Authorization header if your backend requires one (for example, Bearer <token>).
  4. Select which signals to export (Metrics, Logs, Traces).
  5. (Optional) Set a sampling rate for traces (default 100%; reduce for high-volume workloads).
  6. Save.
Telemetry flows to your backend immediately - no restart required.

​
Common backends

Check your backend’s documentation for the exact endpoint URL and auth header format.

​
What to dashboard

​
Trace sampling

100% trace sampling on a busy workspace can be expensive (bandwidth, ingestion cost). Typical settings: You can also use error-based sampling - capture 100% of failed queries but a fraction of successful ones - configured in the OTel sampling settings or via your collector.

​
Privacy and compliance

Telemetry contains query metadata (timing, status, user identity) but not query text by default. To include query text in traces, enable Include query text in spans in the observability settings - this may expose sensitive SQL to your backend, so review compliance implications first. Query results are never exported.

​
See also

Last modified on September 29, 2026