Getting Started
Note that if your backend expects OTLP over http you should use the OTLP http destination instead.
Configuring Destination Fields
Supported Signals:
Supported Signals:
✅ Traces
✅ Metrics
✅ Logs
- OTLP_GRPC_ENDPOINT
string: OTLP gRPC Endpoint. The format ishost:port, host is required, port is optional and defaults to the default OTLP gRPC port4317.- This field is required
- Example:
host:port
- OTLP_GRPC_COMPRESSION
string: Destination Compression Type. Compression type to use for the destination. The default isnone. The compression type must be supported by the destination.- This field is optional and defaults to
none
- This field is optional and defaults to
- OTLP_GRPC_HEADERS
{ key: string; value: string; }[]: Headers. Headers is the option to set custom GRPC headers for OTLP GRPC destination. If specified, please provide each header in the format: key:value. Multiple headers can be added. Keys must be non-empty strings and follow standard HTTP header conventions. Values must be non-empty strings and may include alphanumerics, whitespace, and standard punctuation.- This field is optional
- OTLP_GRPC_OAUTH2_ENABLED
boolean: Enable OAuth2. Enable OAuth2 client credentials authentication- This field is optional and defaults to
False
- This field is optional and defaults to
- OTLP_GRPC_OAUTH2_CLIENT_ID
string: OAuth2 Client ID. OAuth2 client identifier for client credentials flow- This field is optional
- Example:
your-client-id
- OTLP_GRPC_OAUTH2_CLIENT_SECRET
string: OAuth2 Client Secret. OAuth2 client secret for client credentials flow- This field is optional
- Example:
your-client-secret
- OTLP_GRPC_OAUTH2_TOKEN_URL
string: OAuth2 Token URL. OAuth2 token endpoint URL for obtaining access tokens- This field is optional
- Example:
https://example.com/oauth2/token
- OTLP_GRPC_OAUTH2_SCOPES
string: OAuth2 Scopes. Comma-separated list of OAuth2 scopes to request (e.g., “api.metrics,api.traces”)- This field is optional
- Example:
api.metrics,api.traces
- OTLP_GRPC_OAUTH2_AUDIENCE
string: OAuth2 Audience. OAuth2 audience parameter for token requests- This field is optional
- Example:
api.example.com
- OTLP_GRPC_TLS_ENABLED
boolean: Enable TLS. Secure connection- This field is optional and defaults to
False
- This field is optional and defaults to
- OTLP_GRPC_CA_PEM
string: Certificate Authority. When using TLS, provide the CA certificate in PEM format to verify the server. If empty uses system root CA- This field is optional
- Example:
-----BEGIN CERTIFICATE-----
- OTLP_GRPC_INSECURE_SKIP_VERIFY
boolean: Insecure Skip Verify. Skip TLS certificate verification- This field is optional and defaults to
False
- This field is optional and defaults to
Adding Destination to Odigos
There are two primary methods for configuring destinations in Odigos:Using the UI
1
Use the Odigos CLI to access the UI
2
Click on
Add Destination, select OTLP gRPC and follow the on-screen instructionsUsing Kubernetes manifests
1
Save the YAML below to a file (e.g.
otlp.yaml)2
Apply the YAML using
kubectl