Source: vercel.com/changelog/vercel-daemons-can-now-send-traces-to-vercel-tracing
Each daemon gets a Unix socket that accepts OTLP/HTTP traces, and its path is set in the VERCEL_OTEL_SOCKET_PATH environment variable. The SDK detects this socket and sends the spans a worker records to Vercel.
The worker still needs to initialize OpenTelemetry with registerOTel from @vercel/otel before it starts, using a service name such as my-daemon. Once that is in place, no extra export code is required for Node.js daemons on the default setup.
The recorded spans can be read with the Vercel CLI. The command vercel traces search --project my-project --service my-daemon --json returns daemon spans from the last hour as JSON, which agents can parse. Vercel points to its daemon tracing documentation for further detail.
Why it matters if you build agents
Developers running background workers can now inspect those workers in the same tracing system they use for the rest of a project, rather than tracking worker runs separately. Upgrading @vercel/otel to 2.3.0 or later is the change that turns on automatic export for Node.js daemons. Agents that query traces through the CLI can pull daemon spans as JSON to check worker activity.
Get stories like this every weekday
One short email with the day's agent tooling news.