What the November 13 release adds
Vercel’s November 13, 2026 release documents support for exporting daemon spans to Vercel Tracing. That is different from merely starting a daemon, and it is different again from seeing console output. A daemon can be running, logging, and still not be exporting the span you expect.
According to the docs, Vercel sets VERCEL_OTEL_SOCKET_PATH to a local OTLP/HTTP Unix socket inside the container. In Node.js, @vercel/otel 2.3.0 or later can use automatic socket export with the default exporter configuration, as long as registration happens before worker work starts. Even then, this does not mean every task will produce a meaningful span.
What is and is not evidence
- A span exported to the intended Vercel project/service is useful evidence.
- A worker log shows that the code reached a logging statement; it does not verify that the expected span was exported.
- A span from another project or service does not verify the daemon you are checking.
- An empty search result is inconclusive until you confirm project, service, time window, exporter destination, and sampling.
Also note that if you explicitly configure an exporter endpoint, the socket is not used per the docs. Before changing configuration, check the intended destination so you do not accidentally bypass the automatic socket path. Non-Node clients need a compatible exporter and OTLP/HTTP; the Unix socket does not support OTLP/gRPC.
How to verify a span in a test deployment
- Use an authorized nonproduction daemon only.
- Choose one harmless, distinctive span name and a matching service name for that daemon.
- Record a UTC timestamp for the test window.
- Run one harmless task that records the named span. End the span and keep secrets and payloads out of its attributes.
- In Vercel Tracing, look for the named span in the expected project, service, and time window. Other spans from the same task can appear too.
- If nothing appears, check the search scope, exporter endpoint, sampling, and whether the span was actually recorded before concluding the daemon failed.
The point is simple: verify one span before relying on tracing. That single exported span is stronger proof than startup logs, but it still needs to match the right project, service, and time window before you trust it as evidence of daemon tracing support.
Source links
Vercel changelog: Vercel Daemons can now send traces to Vercel Tracing
