Skip to main content

​
Getting Started

dynamic Use Dynamic Destination when you need a collector exporter configuration that is not covered by a built-in destination type (for example, OTLP with client mTLS via freeform YAML).
Environment variable placeholders such as ${OTLP_CA_PEM} in DYNAMIC_CONFIGURATION_DATA are expanded by the gateway collector from pod environment variables. To inject those values, create a Secret in the same namespace as the Destination (the Odigos system namespace) whose keys match the placeholder names, and set spec.secretRef.name on the Destination. Without secretRef, the autoscaler will not mount the Secret into the gateway and the placeholders remain unset.

​
Configuring Destination Fields

✅ Traces ✅ Metrics ✅ Logs ✅ Profiles
  • DYNAMIC_DESTINATION_TYPE string : Destination Type. The type of OpenTelemetry Collector Exporter to use for the destination.
    • This field is required
    • Example: otlp
  • DYNAMIC_CONFIGURATION_DATA string : Config. The raw YAML config for the Collector Exporter for this destination. To inject secrets (e.g. TLS PEMs), use $ placeholders and set Destination.spec.secretRef to a Secret in the same namespace whose keys match those variable names.
    • This field is required

​
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 Dynamic Destination and follow the on-screen instructions
Using Kubernetes manifests
1
Save the YAML below to a file (e.g. dynamic.yaml)
2
Apply the YAML using kubectl