Vercel Daemons export worker spans through a local socket
Vercel Daemons can now send background-worker traces to Vercel Tracing through a supplied Unix socket. For Node.js workers using default configuration, @vercel/otel 2.3.0 or later detects the socket and exports recorded spans automatically. Teams can search those spans by service name through the CLI, bringing worker activity into the same project-level view as other traces.
Vercel · Nov 13, 2026
Why it matters
A background job’s slow or failed operation becomes easier to investigate alongside the request that triggered it.
More context
Upgrade the telemetry package and initialize OpenTelemetry before the worker starts. Try one instrumented operation, then search its service name in the project’s traces. The socket path is supplied through VERCEL_OTEL_SOCKET_PATH; it transports OTLP over HTTP.
Keep in mind
Released hosted-platform capability. Automatic export does not mean every application operation is automatically instrumented. The announcement does not establish new retention guarantees or changes to tracing costs.
Original read