Causely - Odigos

Getting Started

This destination is for the Causely Mediator Service, so you will need to have a Causely instance running and accessible from the k8s cluster running Odigos.

Configuring Destination Fields

Supported Signals:

✅ Traces ✅ Metrics ❌ Logs ❌ Profiles

CAUSELY_URL string : Endpoint. The endpoint URL is the combined <protocol>://<hostname>:<port> to access your Causely Mediator service. Protocol should be http; using https or omitting it will automatically be converted to http. Hostname should typically follow the format: mediator.<namespace>. Namespace is the k8s namespace where the Causely Mediator service is deployed. Port is optional and defaults to the default OTLP gRPC port 4317
- This field is required
- Example: http://mediator.causely:4317

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

Using Kubernetes manifests

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

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

Apply the YAML using kubectl

kubectl apply -f causely.yaml

Bonree ONE Checkly

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos