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
Docs
About the Eve integration
@telemetry-dev/eve wires Vercel's Eve agent framework to telemetry.dev through Eve's native OpenTelemetry, lifecycle-hook, and HTTP-client surfaces. A typical turn produces an invoke_agent root span with nested model-call and execute_tool spans, usage attributes, TTFT, and lifecycle logs joined to the same session via gen_ai.conversation.id.
Key features
- Server instrumentation in one file: Export
telemetryDevInstrumentation()fromagent/instrumentation.tsand 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-sideinvoke_agentspan persession.send()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
onErrorand never throw back into Eve; no API key means a complete no-op.
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.19.0 and Node.js 24+.