​
Getting Started

​
Configuring Destination Fields

  • OBSERVE_CUSTOMER_ID string : Customer ID. The Customer ID is the first part of your Observe URL. For example, if your Observe URL is https://<customer_id>.observe.com, then the Customer ID is <customer_id>.
    • This field is required
  • OBSERVE_TOKEN string : Token. You can create a token in your Observe dashboard, under “Datastreams”.
    • This field is required

We handle the endpoint internally, so you don’t need to provide it.

  • The endpoint is https://${OBSERVE_CUSTOMER_ID}.collect.observeinc.com/v2/otel

​
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 Observe and follow the on-screen instructions

Using Kubernetes manifests
1

Save the YAML below to a file (e.g. observe.yaml)

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: observe-example
  namespace: odigos-system
spec:
  data:
    OBSERVE_CUSTOMER_ID: <Customer ID>
  destinationName: observe
  secretRef:
    name: observe-secret
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: observe

---

apiVersion: v1
data:
  OBSERVE_TOKEN: <Base64 Token>
kind: Secret
metadata:
  name: observe-secret
  namespace: odigos-system
type: Opaque
2

Apply the YAML using kubectl

kubectl apply -f observe.yaml