For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.
Sample tracing configs
Sample configurations for exporting agentgateway traces to common OTLP-compatible backends, including OpenTelemetry Collector, Jaeger, and SaaS platforms.
Agentgateway exports traces to any OTLP-compatible backend. The host value in frontendPolicies.tracing depends on how you installed agentgateway and where your OTLP receiver is running.
| Install method | host value | Notes |
|---|---|---|
| Binary | localhost:4317 | Run the OTLP receiver as a separate process or Docker container on the same host. |
| Docker Compose | <service-name>:4317 | Add the receiver as a service that runs alongside agentgateway. Use the Docker service name as the host. |
| Kubernetes (Helm) | <service>.<namespace>.svc.cluster.local:4317 | Deploy the OTLP receiver as a separate Helm release. For example, you can install the Jaeger Helm chart that includes an OTLP receiver and the Jaeger UI to view your traces. Use the Kubernetes service DNS name as your host. |
Choose one of the following guides to configure your tracing backend.
OpenTelemetry Collector (OTel)
Route agentgateway traces through an OpenTelemetry Collector to fan out to multiple backends or …
Jaeger
Export agentgateway traces to Jaeger for local collection and visualization by using its built-in …
SaaS platform
Export agentgateway traces to a cloud-hosted SaaS observability platform such as Langfuse over …
