Vercel Daemons can now send OpenTelemetry traces to Vercel Tracing, allowing you and your agents to inspect background worker operations alongside the rest of your project's traces.
Vercel provides each daemon with a Unix socket for receiving OTLP/HTTP traces and sets the socket's path in VERCEL_OTEL_SOCKET_PATH.
Upgrading @vercel/otel to version 2.3.0 or later enables automatic trace export for Node.js daemons using the default configuration. The SDK detects this socket and sends the spans your worker records to Vercel.
import { registerOTel } from '@vercel/otel';
registerOTel({ serviceName: 'my-daemon' });Initialize OpenTelemetry before the worker starts.
These spans are available through the Vercel CLI, which can search by service name within a project and return JSON for your agents.
vercel traces search --project my-project --service my-daemon --jsonSearch daemon spans from the last hour as JSON.
Learn more in the daemon tracing documentation.
Reference Architecture
Choose a stack and work through the decisions behind it, with curated documentation, guides, templates, and courses to help you build.
- Agent stack: Build and operate agents with models, tools, and durable workflows.
- Web applications: Choose rendering, data, authentication, and caching approaches.
- Backends: Choose a runtime, connect services, and run background work.
Build with prompts
Build an app, extend an agent, or improve your project with ready-to-use prompts for your coding agent.