Skip to main content
This is an advanced configuration method. Most users should use Remote Configuration via the dashboard instead.
Environment variables provide an alternative way to configure OpenTelemetry, useful for self-hosted deployments, local development, CI/CD pipelines, or when you need to override organization settings.

When to Use

  • Self-hosted deployments without dashboard access
  • Local development and testing with your own collectors
  • CI/CD pipelines that need observability
  • Override organization settings with user-specific configuration
Environment variable configuration bypasses user telemetry settings and will export data regardless of individual preferences.

Environment Variables

Core Configuration

OTLP Configuration

Advanced OTLP Configuration

For separate metrics and logs endpoints:

Export Tuning

Quick Start Examples

Datadog with gRPC

The endpoint shown above is for Datadog’s US1 region. If you’re in a different region (EU, US3, US5, AP1, etc.), replace api.datadoghq.com with your region-specific hostname (e.g., api.datadoghq.eu for EU). See Datadog’s OTLP documentation for your region’s endpoint.

New Relic with HTTP

Local Development (Insecure)

Console Output (Testing)

Debugging

Enable detailed OpenTelemetry diagnostic logging:
This outputs:
  • Configuration being used
  • Exporters being created
  • Connection attempts
  • Export successes/failures
Check the VS Code Developer Tools Console (Help > Toggle Developer Tools) for diagnostic output.

Configuration Priority

When multiple configuration methods are present, Cline uses this priority order:
  1. Environment variables (highest priority) - This method
  2. Remote Configuration - Dashboard settings
  3. Default settings - Built-in defaults
Environment variable configuration will override dashboard settings.

See Also

Dashboard Configuration

Configure OpenTelemetry via the web dashboard

Remote Configuration

Learn about Remote Configuration system