OneUptime - Odigos

Getting Started

Configuring Destination Fields

Supported Signals:

✅ Traces ✅ Metrics ✅ Logs ❌ Profiles

ONEUPTIME_INGESTION_KEY string : Telemetry Ingestion Key. The Telemetry Ingestion Key is used to authenticate your data. You can find it in the OneUptime dashboard under Project Settings > Ingestion Keys.
- This field is required

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

The endpoint is https://oneuptime.com/otlp

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

Using Kubernetes manifests

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

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

---

apiVersion: v1
data:
  ONEUPTIME_INGESTION_KEY: <Base64 Telemetry Ingestion Key>
kind: Secret
metadata:
  name: oneuptime-secret
  namespace: odigos-system
type: Opaque

Apply the YAML using kubectl

kubectl apply -f oneuptime.yaml

Observe OpenObserve

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos