For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.
Honeycomb
Configure agentgateway to send traces to Honeycomb.
Honeycomb is an observability platform. You can send traces to the Honeycomb OTLP API from the agentgateway proxy via an OpenTelemetry Collector.
Note
Honeycomb requires an x-honeycomb-team header on every OTLP request. Because the agentgateway tracing policy does not support custom HTTP headers, you must route traces through an OTel Collector that injects the header before forwarding to Honeycomb.
Before you begin
- Set up an agentgateway proxy.
- Install the httpbin sample app.
Configure tracing
Step 1: Set up the OTel Collector
Follow the OTel Collector setup guide to install a collector in your cluster. Then update the collector’s exporter config to forward traces to Honeycomb with your API key.
In Honeycomb, go to Account → Team Settings to find or create an API key. Add the following exporter to your collector config.
exporters: otlp/honeycomb: endpoint: https://api.honeycomb.io:443 headers: x-honeycomb-team: "<your-honeycomb-api-key>"
Step 2: Point the tracing policy at the collector
Create an AgentgatewayPolicy that points the agentgateway proxy at the OTel Collector.
kubectl apply -f- <<EOF
apiVersion: agentgateway.dev/v1alpha1
kind: AgentgatewayPolicy
metadata:
name: tracing
namespace: agentgateway-system
spec:
targetRefs:
- kind: Gateway
name: agentgateway-proxy
group: gateway.networking.k8s.io
frontend:
tracing:
backendRef:
name: opentelemetry-collector
namespace: tracing
port: 4317
protocol: GRPC
randomSampling: "true"
EOFCleanup
You can remove the resources that you created in this guide.kubectl delete AgentgatewayPolicy tracing -n agentgateway-system