---
title: Honeycomb
description: Send OpenTelemetry traces to Honeycomb and query every agent turn.
type: instrumentation
keywords:
  - otel
  - opentelemetry
  - tracing
  - observability
  - queries
  - otlp
---

# Honeycomb

Instrumentation integration for eve. Send OpenTelemetry traces to Honeycomb and query every agent turn.

## Install

Add Honeycomb instrumentation from eve's registry. Honeycomb ingests OTLP directly:

```bash
eve add instrumentation/honeycomb
```

## Quick start

Create `agent/instrumentation.ts` and send traces to Honeycomb's OTLP endpoint with your ingest key:

```ts
// agent/instrumentation.ts
import { defineInstrumentation } from "eve/instrumentation";
import { OTLPHttpProtoTraceExporter, registerOTel } from "@vercel/otel";

export default defineInstrumentation({
  setup: ({ agentName }) =>
    registerOTel({
      serviceName: agentName,
      traceExporter: new OTLPHttpProtoTraceExporter({
        url: "https://api.honeycomb.io/v1/traces",
        headers: { "x-honeycomb-team": process.env.HONEYCOMB_API_KEY! },
      }),
    }),
});
```

## Configure

Create an ingest key under your Honeycomb environment settings and expose it as `HONEYCOMB_API_KEY`. Spans arrive in a dataset named after your agent (the OTel service name). EU teams use `https://api.eu1.honeycomb.io/v1/traces`. See the [instrumentation guide](/docs/guides/instrumentation) for the trace hierarchy and the `recordInputs`/`recordOutputs` controls.

[Read the full instrumentation documentation](/docs/guides/instrumentation)

---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)