Better Stack - Odigos

Getting Started

Configuring Destination Fields

Supported Signals:

❌ Traces ✅ Metrics ✅ Logs ❌ Profiles

BETTERSTACK_TOKEN string : Better Stack Source Token.
- This field is required

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

The endpoint for metrics is https://in-otel.logs.betterstack.com/metrics
The endpoint for logs is https://in-otel.logs.betterstack.com:443

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 Better Stack and follow the on-screen instructions

Using Kubernetes manifests

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

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: betterstack-example
  namespace: odigos-system
spec:
  data: {}
  destinationName: betterstack
  secretRef:
    name: betterstack-secret
  signals:
  - METRICS
  - LOGS
  type: betterstack

---

apiVersion: v1
data:
  BETTERSTACK_TOKEN: <Base64 Better Stack Source Token>
kind: Secret
metadata:
  name: betterstack-secret
  namespace: odigos-system
type: Opaque

Apply the YAML using kubectl

kubectl apply -f betterstack.yaml

Azure Monitor Bonree ONE

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos