Supported Backends
Jaeger
Configuring the Jaeger backend (Self-Hosted)
Getting Started
Version v1.35 of Jaeger introduced the ability to receive OpenTelemetry trace data via the OpenTelemetry Protocol (OTLP). This allows to create a new Jaeger backend by simply specifying the Jaeger OTLP gRPC unencrypted URL.
Configuring Destination Fields
- JAEGER_URL
string
: Jaeger 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
- JAEGER_TLS_ENABLED
boolean
: Enable TLS. Secure connection- This field is optional
- JAEGER_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-----
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 Jaeger
and follow the on-screen instructions
Using Kubernetes manifests
1
Save the YAML below to a file (e.g. jaeger.yaml
)
2
Apply the YAML using kubectl