OTLP bridge
If your services already emit OpenTelemetry, avuru obs is a drop-in OTLP backend. Change the endpoint — nothing else.
# OTLP/HTTP
export OTEL_EXPORTER_OTLP_ENDPOINT=http://avuruobs-gateway:4318
# OTLP/gRPC
export OTEL_EXPORTER_OTLP_ENDPOINT=http://avuruobs-gateway:4317
export OTEL_EXPORTER_OTLP_PROTOCOL=grpc
This works for traces, metrics and logs. Spans you export land next to the
eBPF-discovered map and share the same service.name resource identity.
Migrating from Jaeger / another OTLP backend
Repoint the exporter endpoint to the gateway. No SDK or code changes are needed — avuru obs speaks native OTLP. For tool-specific migration notes and side-by-side comparisons, see Compare (Jaeger, the Grafana stack, Prometheus, Datadog).
:::note This page is expanding Per-language exporter snippets live under Integrations. Sampling and tail-based sampling guidance is being added to Traces. :::