Supported Backends
Quickwit
Configuring Quickwit Backend
The only required field is the Quickwit endpoint which is supporting OTLP grpc (which should be unencrypted).
This endpoint must be a valid URL without scheme for your Quickwit cluster, i.e: {quickwit_host}:7281
You’ll find more details here: https://quickwit.io/docs/log-management/otel-service
Adding a Destination to Odigos
Odigos makes it simple to add and configure destinations, allowing you to select the specific signals [traces/logs/metrics] that you want to send to each destination. There are two primary methods for configuring destinations in Odigos:
- Using the UI
To add a destination via the UI, follow these steps:- Use the Odigos CLI to access the UI: Odigos UI
odigos ui
-
In the left sidebar, navigate to the
Destination
page. -
Click
Add New Destination
-
Select
Quickwit
and follow the on-screen instructions.
- Using kubernetes manifests
Save the YAML below to a file (e.g., destination.yaml
) and apply it using kubectl
:
kubectl apply -f destination.yaml
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
name: quickwit-example
namespace: odigos-system
spec:
data:
QUICKWIT_URL: <Quickwit OTLP gRPC Endpoint>
destinationName: quickwit
signals:
- TRACES
- LOGS
type: quickwit