Self-managed installation and maintenance > Enterprise monitoring guide > Generic OTLP endpoint

Generic OTLP endpoint¶

This section shows how to configure the chart to export telemetry to a generic OTLP ingestion endpoint. This is suitable for any backend that supports the OTLP protocol.

Full chart configuration¶

The following configuration is added to the datarobot-prime chart values. Replace the placeholder values with the actual values.

For additional exporter configuration options, refer to the upstream OpenTelemetry documentation for the otlp and otlphttp exporters.

Using gRPC (OTLP)¶

global:
  observability:
    exporters:
      otlp:
        endpoint: <OTLP_GRPC_ENDPOINT>
        tls:
          insecure: false

    signals:
      logs:
        exporters: [otlp]
      metrics:
        exporters: [otlp]
      traces:
        exporters: [otlp]

Using HTTP (OTLP/HTTP)¶

global:
  observability:
    exporters:
      otlphttp:
        endpoint: <OTLP_HTTP_ENDPOINT>

    signals:
      logs:
        exporters: [otlphttp]
      metrics:
        exporters: [otlphttp]
      traces:
        exporters: [otlphttp]

Where:

<OTLP_GRPC_ENDPOINT>: the gRPC endpoint (e.g. otel-collector.example.com:4317)
<OTLP_HTTP_ENDPOINT>: the HTTP endpoint (e.g. https://otel-collector.example.com:4318)

With authentication headers¶

If the endpoint requires an API key or bearer token, store it in a Kubernetes secret and reference it via the secrets section:

kubectl create secret -n <DR_CORE_NAMESPACE> generic datarobot-otlp \
  --from-literal=api-key="<API_KEY>"

global:
  observability:
    secrets:
      - envVar: OTLP_API_KEY
        secretName: datarobot-otlp
        secretKey: api-key

    exporters:
      otlphttp:
        endpoint: <OTLP_HTTP_ENDPOINT>
        headers:
          Authorization: Bearer ${env:OTLP_API_KEY}

    signals:
      logs:
        exporters: [otlphttp]
      metrics:
        exporters: [otlphttp]
      traces:
        exporters: [otlphttp]