Tempo

Getting Started

These instructions are for the self hosted Tempo instance. If you need a managed service, please follow the instructions on the Grafana Cloud Tempo page.

Configuring Destination Fields

Supported Signals:

✅ Traces ❌ Metrics ❌ Logs ❌ Profiles

TEMPO_URL string : Endpoint.
- This field is required

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

Using Kubernetes manifests

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

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: tempo-example
  namespace: odigos-system
spec:
  data:
    TEMPO_URL: <Endpoint>
  destinationName: tempo
  signals:
  - TRACES
  type: tempo

Apply the YAML using kubectl

kubectl apply -f tempo.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