
Background workers on Vercel have always run silently. You could see whether a daemon succeeded or failed, but not what happened inside it. That changes today.
Vercel Daemons can now send OpenTelemetry traces to Vercel Tracing, so every slow database query, external API call, and queue handler step shows up alongside the rest of your project’s traces.
Source: Read the official announcement.
How it works
Vercel gives each daemon a Unix socket for OTLP/HTTP traces. The path is set in the VERCEL_OTEL_SOCKET_PATH environment variable. If you run a Node.js daemon, upgrade @vercel/otel to version 2.3.0 or later. The SDK detects the socket and exports spans from your worker without extra configuration.
import { registerOTel } from '@vercel/otel';
registerOTel({ serviceName: 'my-daemon' });
Call this before your worker starts. From that point, every span your daemon creates is collected.
You can search the resulting traces through the Vercel CLI. The command below returns JSON for a specific service within a project, covering the last hour.
vercel traces search --project my-project --service my-daemon --json
That search is useful for agents as well as humans. You can pipe it into an AI tool or a Slack alert without parsing a dashboard.
This update lands in the same week as several other Vercel improvements, including a build cache increase to 5 GB and faster sandbox startup times.
Frequently asked questions
What is Vercel Daemon tracing? It is the ability to collect OpenTelemetry traces from your background workers and view them inside Vercel Tracing, alongside the traces from your serverless functions and edge middleware.
How do I enable traces for my daemons?
Upgrade @vercel/otel to version 2.3.0 or later, then call registerOTel with a service name inside your worker entry file. The SDK reads the VERCEL_OTEL_SOCKET_PATH environment variable and exports traces automatically.
Which daemons support this?
The automatic export works for Node.js daemons. For other runtimes, you can send OTLP/HTTP traces to the Unix socket manually by using the path in VERCEL_OTEL_SOCKET_PATH.
Sources
3 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.






