KloudMate

Getting Started

Configuring Destination Fields

Supported Signals:

✅ Traces ✅ Metrics ✅ Logs ❌ Profiles

KLOUDMATE_API_KEY string : KloudMate API Key.
- This field is required

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

The endpoint is https://otel.kloudmate.com:4318

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

Using Kubernetes manifests

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

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

---

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

Apply the YAML using kubectl

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