​
Obtaining Last9 OpenTelemetry Endpoint and Basic Auth Header

Click here to visit the Last9 OpenTelemetry integration page.

​
Configuring Last9 Backend

  • Endpoint - Last9 OpenTelemetry Endpoint obtained in above step.
  • Authorization Header: Last9 OpenTelemetry Basic Auth Header obtained in above step.

​
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 To add a destination via the UI, follow these steps:
    • Use the Odigos CLI to access the UI: Odigos UI
    odigos ui

  • In the left sidebar, navigate to the Destination page.

  • Click Add New Destination

  • Select Last9 and follow the on-screen instructions.

  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: last9-example
  namespace: odigos-system
spec:
  data:
    LAST9_OTLP_ENDPOINT: <Last9 OpenTelemetry Endpoint>
  destinationName: last9
  secretRef:
    name: last9-secret
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: last9

---
apiVersion: v1
data:
  LAST9_OTLP_BASIC_AUTH_HEADER: <base64 Basic Auth Header>
kind: Secret
metadata:
  name: last9-secret
  namespace: odigos-system
type: Opaque
JaegerLightstep