Dash0 - Odigos

Getting Started

Configuring Destination Fields

Supported Signals:

✅ Traces ✅ Metrics ✅ Logs ❌ Profiles

DASH0_ENDPOINT string : Dash0 OTLP 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.
- This field is required
DASH0_TOKEN string : Dash0 Bearer Token. Located in Dash0 UI (OpenTelemetry Collector).
- This field is required

Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:

Using the UI

Use the Odigos CLI to access the UI

odigos ui

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

Using Kubernetes manifests

Save the YAML below to a file (e.g. dash0.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

Apply the YAML using kubectl

kubectl apply -f dash0.yaml

Coralogix Datadog

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos