Skip to main content
TrueFoundry AI Gateway can export OpenTelemetry traces for LLM gateway traffic. HoneyHive ingests OTLP/HTTP traces directly, so requests routed through TrueFoundry can appear in HoneyHive without adding HoneyHive SDK code to each application.

​
Quick Start

Trace AI Gateway traffic with no SDK code in your application. Point TrueFoundry’s OTEL exporter at HoneyHive and gateway requests start appearing in the Traces tab.

​
Prerequisites

​
Provider host and OTLP traces URL

HoneyHive routes OTLP ingestion through your deployment’s API host. Replace <provider-host> with the hostname shown in your HoneyHive dashboard or API settings:
Example for a US production deployment:
Use the exact host for your org and environment. If ingest fails, confirm the hostname matches the region where your project lives.

​
Configure TrueFoundry

1

Create a HoneyHive ingestion API key

In HoneyHive, open Settings → Project → API Keys, click Create API Key on the Ingestion tab, and copy the key. The key determines which HoneyHive project receives traces, and an ingestion key can do nothing else.
2

Open the TrueFoundry OTEL settings

In TrueFoundry, go to AI Gateway → Controls → Settings, then edit OTEL Config.
3

Enable HTTP trace export

Enable Otel Traces Exporter Configuration, select HTTP Configuration, and set:
4

Add the HoneyHive authorization header

Enable headers and add:Replace <HH_INGESTION_API_KEY> with the ingestion API key from HoneyHive.
5

Save and send gateway traffic

Save the TrueFoundry OTEL configuration, then send a few requests through the AI Gateway.

​
Verify traces in HoneyHive

Open HoneyHive and go to the Traces tab for the project tied to your API key. New gateway spans appear with source set to otlp.
HoneyHive Traces Events view showing OTLP events exported from gateway traffic
If traces do not appear:
  1. Confirm the TrueFoundry endpoint uses your HoneyHive API host and ends with /opentelemetry/v1/traces.
  2. Confirm the header is exactly Authorization: Bearer <HH_INGESTION_API_KEY>.
  3. Confirm the API key was created in the HoneyHive project where you expect the traces to appear.
  4. Check that your gateway can reach the HoneyHive API host over outbound HTTPS.

​
Configuration reference

OpenTelemetry concepts

Learn how HoneyHive stores OTLP traces and AI span attributes

Distributed tracing

Connect gateway spans with application spans across services

Custom spans

Add HoneyHive spans around business logic in your application

​
Resources