OpenObserve

Getting Started

Configuring Destination Fields

Supported Signals:

✅ Traces ❌ Metrics ✅ Logs ❌ Profiles

OPEN_OBSERVE_ENDPOINT string : OTLP HTTP Endpoint.
- This field is required
- Example: https://api.openobserve.ai/api/<organization_id>
OPEN_OBSERVE_API_KEY string : API Key. Do not include the Basic prefix.
- This field is required
OPEN_OBSERVE_STREAM_NAME string : Stream Name.
- This field is required and defaults to default

Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:

Using the UI

Use the Odigos CLI to access the UI

odigos ui

Click on Add Destination, select OpenObserve and follow the on-screen instructions

Using Kubernetes manifests

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

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: openobserve-example
  namespace: odigos-system
spec:
  data:
    OPEN_OBSERVE_ENDPOINT: <OTLP HTTP Endpoint>
    OPEN_OBSERVE_STREAM_NAME: '<Stream Name (default: default)>'
  destinationName: openobserve
  secretRef:
    name: openobserve-secret
  signals:
  - TRACES
  - LOGS
  type: openobserve

---

apiVersion: v1
data:
  OPEN_OBSERVE_API_KEY: <Base64 API Key>
kind: Secret
metadata:
  name: openobserve-secret
  namespace: odigos-system
type: Opaque

Apply the YAML using kubectl

kubectl apply -f openobserve.yaml

Getting Started

Instrumentations

Odigos Pipeline

Destinations

Concepts

Contribution Guidelines

Getting Started

Configuring Destination Fields

Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos