Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.odigos.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Getting Started

jaeger 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

✅ Traces ❌ Metrics ❌ Logs
  • JAEGER_URL string : Jaeger 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
  • JAEGER_TLS_ENABLED boolean : Enable TLS. Secure connection
    • This field is optional and defaults to False
  • 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
odigos 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)
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: jaeger-example
  namespace: odigos-system
spec:
  data:
    JAEGER_URL: <Jaeger OTLP gRPC Endpoint>
    # Note: The commented fields below are optional.
    # JAEGER_TLS_ENABLED: <Enable TLS>
    # JAEGER_CA_PEM: <Certificate Authority>
  destinationName: jaeger
  signals:
  - TRACES
  type: jaeger
2
Apply the YAML using kubectl
kubectl apply -f jaeger.yaml