Observe

​

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. A Datastream ingest token (not a user/API token). Create one in the Observe UI under “Datastreams”. See https://docs.observeinc.com/docs/configure-your-own-otel-collector-in-a-non-kubernetes-environment for how to create an ingest token.
  • This field is required
• OBSERVE_ENDPOINT string : Collection Endpoint. Optional. The full OTLP/HTTP collection endpoint. Set this to override the default, for example for a regional tenant such as https://<customer_id>.collect.eu1.observeinc.com/v2/otel. When empty, it is derived from the Customer ID. See https://docs.observeinc.com/docs/configure-your-own-otel-collector for the endpoint format.
  • This field is optional
  • Example: https://<customer_id>.collect.observeinc.com/v2/otel

​

Adding Destination to Odigos

Using the UI

odigos ui

Using Kubernetes manifests

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: observe-example
  namespace: odigos-system
spec:
  data:
    OBSERVE_CUSTOMER_ID: <Customer ID>
    # Note: The commented fields below are optional.
    # OBSERVE_ENDPOINT: <Collection Endpoint>
  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

kubectl apply -f observe.yaml