Configuring the Causely backend (Managed)
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.
Supported Signals:
✅ Traces ✅ Metrics ❌ Logs
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
http://mediator.causely:4317
There are two primary methods for configuring destinations in Odigos:
Use the Odigos CLI to access the UI
Click on Add Destination
, select Causely
and follow the on-screen instructions
Save the YAML below to a file (e.g. causely.yaml
)
Apply the YAML using kubectl
Configuring the Causely backend (Managed)
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.
Supported Signals:
✅ Traces ✅ Metrics ❌ Logs
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
http://mediator.causely:4317
There are two primary methods for configuring destinations in Odigos:
Use the Odigos CLI to access the UI
Click on Add Destination
, select Causely
and follow the on-screen instructions
Save the YAML below to a file (e.g. causely.yaml
)
Apply the YAML using kubectl