OpenTelemetry Configuration

Logs, traces and metrics are emitted using the OpenTelemetry protocol. This page describes how to configure telemetry collection and export.

OTLP Endpoint Configuration

To configure where to send these signals, set the OTEL_EXPORTER_OTLP_ENDPOINT environment variable on the following components:

controller:
  # ...
  env:
    - name: OTEL_EXPORTER_OTLP_ENDPOINT
      value: http://your-otel-endpoint:4317
    # Isolates' signals are sent to the proxy to be relayed for security reasons.
    # The proxy needs to know where to send those signals.
    - name: OTEL_RELAY_UPSTREAM_URL
      value: http://your-otel-endpoint:4318

proxy:
  # ...
  env:
    - name: OTEL_EXPORTER_OTLP_ENDPOINT
      value: http://your-otel-endpoint:4317

Common Collection Targets

You can configure OpenTelemetry to export to various backends:

• Honeycomb
• Datadog
• New Relic
• Grafana Cloud
• Your own OpenTelemetry Collector

Refer to the specific documentation for your chosen observability platform for details on setting up the OTLP endpoint.

Signal Types

The system emits three types of telemetry signals:

1. Metrics - Performance data including request counts, latencies, memory usage, etc.
2. Traces - Distributed tracing information for requests showing the path through various system components
3. Logs - Structured logs from each component

Related Links

• Controller Configuration
• Internals