E

Eve

Wire Vercel's Eve agent framework to telemetry.dev. Server traces, lifecycle logs, and client-side agent spans — one integration, three surfaces.

Built by

telemetry.dev

Language

TypeScript

Packages

@telemetry-dev/eve

Category

AI frameworks

About the Eve integration

@telemetry-dev/eve connects Eve to telemetry.dev through OpenTelemetry, lifecycle hooks, and HTTP clients. A turn includes spans, usage, TTFT, and session logs.

Key features

  • Server instrumentation in one file: Export telemetryDevInstrumentation() from agent/instrumentation.ts and Eve's tracer scope plus the AI SDK GenAI scope export to telemetry.dev.
  • Lifecycle logs: telemetryDevHook() emits bounded logs for session/turn/step lifecycle, tool results, HITL requests, subagent calls, and compaction — every log carries conversation id and agent name.
  • Client wrapper: wrapEveClient() creates a caller-side invoke_agent span per sessions.create(), send(), or respond() turn, with TTFT from the first delta and usage accumulated from step completions.
  • AI-centric traces: Eve's internal workflow-engine spans are excluded by default so traces stay readable; opt them in with spanFilter: () => true.
  • Fail-open: Hook handlers route errors to onError and never throw back into Eve; no API key means a complete no-op.

Eve 0.50 gives its provider integration no parent-context hook. Thus, provider-style spans cannot join the deterministic telemetry.dev session trace.

Get started

Create agent/instrumentation.ts:

import { telemetryDevInstrumentation } from "@telemetry-dev/eve";

export default telemetryDevInstrumentation();

Optionally add lifecycle logs in agent/hooks/telemetry-dev.ts:

import { telemetryDevHook } from "@telemetry-dev/eve";

export default telemetryDevHook();

Set TELEMETRY_DEV_API_KEY and run your agent. Requires eve >= 0.47.0 and Node.js 24+.