​
Configuring Backend

  • DASH0_ENDPOINT - OpenTelemetry gRPC Endpoint, the format is host:port.
    • host is required, located in Dash0 UI - OpenTelemetry Collector.
    • port is optional and defaults to the default OTLP gRPC port 4317.
  • DASH0_TOKEN - Dash0 Authorization Token, located in Dash0 UI - OpenTelemetry Collector.

​
Adding a Destination to Odigos

Odigos makes it simple to add and configure destinations, allowing you to select the specific signals [traces/logs/metrics] that you want to send to each destination. There are two primary methods for configuring destinations in Odigos:

  1. Using the UI

Use the Odigos CLI to access the UI:

odigos ui
  1. Using kubernetes manifests

Save the YAML below to a file (e.g., destination.yaml) and apply it using kubectl:

kubectl apply -f destination.yaml

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: dash0-example
  namespace: odigos-system
spec:
  data:
    DASH0_ENDPOINT: <Dash0 OTLP gRPC Endpoint>
  destinationName: dash0
  secretRef:
    name: dash0-secret
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: dash0

---
apiVersion: v1
data:
  DASH0_TOKEN: <base64 Dash0 Bearer Token>
kind: Secret
metadata:
  name: dash0-secret
  namespace: odigos-system
type: Opaque
CoralogixDatadog