​
Configuring Jaeger Backend

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.

  • JAEGER_URL - Endpoint, the format is host:port.
    • host is required
    • port is optional and defaults to the default OTLP gRPC port 4317.
  • JAEGER_TLS_ENABLED - Enable TLS (secure connection). This is optional and defaults to false.
  • JAEGER_CA_PEM - Certificate Authority in PEM format. When using TLS, provide the CA certificate to verify the server. If empty uses system root CA

​
Adding a Destination to Odigos

Odigos makes it simple to add and configure destinations, allowing you to select the specific signals [traces/logs/metrics] that you want to send to each destination. There are two primary methods for configuring destinations in Odigos:

  1. Using the UI

Use the Odigos CLI to access the UI:

odigos ui
  1. Using kubernetes manifests

Save the YAML below to a file (e.g., destination.yaml) and apply it using kubectl:

kubectl apply -f destination.yaml

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: jaeger-example
  namespace: odigos-system
spec:
  data:
    JAEGER_URL: <Jaeger OTLP gRPC Endpoint>
    # JAEGER_TLS_ENABLED: <Enable TLS (secure connection)>
    # JAEGER_CA_PEM: <Certificate Authority>
    # Note: The commented fields above are optional.
  destinationName: jaeger
  signals:
  - TRACES
  type: jaeger
HoneycombLast9