​
Getting Started

For advanced users trying to implement complex observability pipelines, Odigos support sending data to any OTLP gRPC unencrypted endpoint.

Note that if your backend expects OTLP over http you should use the OTLP http destination instead.

If your backend is supported natively in Odigos, it’s recommended to use the native integration.

​
Configuring Destination Fields

  • OTLP_GRPC_ENDPOINT string : OTLP gRPC Endpoint. The format is host:port, host is required, port is optional and defaults to the default OTLP gRPC port 4317.
    • This field is required
    • Example: host:port

​
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

odigos ui
2

Click on Add Destination, select OTLP gRPC and follow the on-screen instructions

Using Kubernetes manifests
1

Save the YAML below to a file (e.g. otlp.yaml)

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: otlp-example
  namespace: odigos-system
spec:
  data:
    OTLP_GRPC_ENDPOINT: <OTLP gRPC Endpoint>
  destinationName: otlp
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: otlp
2

Apply the YAML using kubectl

kubectl apply -f otlp.yaml
OpsVerseOTLP http