​

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 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

odigos ui

Using Kubernetes manifests

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

kubectl apply -f jaeger.yaml