Vercel Daemons can now send OpenTelemetry traces to Vercel Tracing
Vercel Daemons can now send OpenTelemetry traces to Vercel Tracing. Each daemon receives a Unix socket for OTLP/HTTP traces, with its path set in the VERCEL_OTEL_SOCKET_PATH environment variable. Upgrading @vercel/otel to version 2.3.0 or later enables automatic trace export for Node.js daemons using the default configuration.

Why it matters
Background worker operations can now be inspected alongside the rest of a project's traces in Vercel Tracing, rather than separately. Traces can be searched by service name within a project through the Vercel CLI, which returns JSON output.
Who should care
Teams running background workers or daemons on Vercel, Node.js developers using @vercel/otel, and developers who use AI agents to inspect project traces.
What you can do
Upgrade @vercel/otel to version 2.3.0 or later in a Node.js daemon, then search its traces by service name with the Vercel CLI.