For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Export agentgateway traces to a cloud-hosted SaaS observability platform such as Langfuse over HTTPS.

Cloud-hosted observability platforms accept OTLP traces over HTTPS and authenticate requests with an Authorization header. The steps below use Langfuse as an example, but the same pattern applies to any OTLP-over-HTTP SaaS backend. Swap in your platform’s endpoint and credentials.

Before you begin

Create a Langfuse account at https://cloud.langfuse.com and create a project. In the dashboard, go to Settings → API Keys and create a key pair. Then base64-encode <public-key>:<secret-key>.

echo -n "<public-key>:<secret-key>" | base64

Keep the encoded string — you will use it as the Authorization header value.

Configure tracing

# yaml-language-server: $schema=https://agentgateway.dev/schema/config
frontendPolicies:
  tracing:
    host: us.cloud.langfuse.com:443
    protocol: http/protobuf
    randomSampling: true
    policies:
      backendTLS: {}
      requestHeaderModifier:
        set:
          Authorization: "Basic <base64-encoded-credentials>"

config:
  frontendPolicies:
    tracing:
      host: us.cloud.langfuse.com:443
      protocol: http/protobuf
      randomSampling: true
      policies:
        backendTLS: {}
        requestHeaderModifier:
          set:
            Authorization: "Basic <base64-encoded-credentials>"

helm upgrade -i agentgateway-standalone \
  oci://cr.agentgateway.dev/charts/agentgateway-standalone \
  --namespace agentgateway-system \
  --version v1.5.0 \
  --reuse-values \
  -f values.yaml

Verify

Send a request through agentgateway and then check Traces in the Langfuse dashboard. Traces typically appear within a few seconds.

Other SaaS backends

The same pattern works for other OTLP-over-HTTPS backends — adjust host, protocol, and the auth header to match your platform.