​
Configuring Backend

  • LUMIGO_ENDPOINT - OpenTelemetry HTTP Endpoint, defaults to https://ga-otlp.lumigo-tracer-edge.golumigo.com.
  • LUMIGO_TOKEN - Lumigo Authorization Token.

​
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: lumigo-example
  namespace: odigos-system
spec:
  data:
    LUMIGO_ENDPOINT: <Lumigo OTLP HTTP Endpoint>
  destinationName: lumigo
  secretRef:
    name: lumigo-secret
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: lumigo

---
apiVersion: v1
data:
  LUMIGO_TOKEN: <base64 Lumigo Token>
kind: Secret
metadata:
  name: lumigo-secret
  namespace: odigos-system
type: Opaque
LokiNew Relic