# Daemons can now send traces to Vercel Tracing

DevFeed: [Daemons can now send traces to Vercel Tracing](<https://devfeed.tech/articles/daemons-can-now-send-traces-to-vercel-tracing-133481.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-daemons-can-now-send-traces-to-vercel-tracing>)

Author: Gal Schlezinger

Published: 2026-11-13T22:24:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [tracing](<https://devfeed.tech/topics/tracing.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [automatic](<https://devfeed.tech/tags/automatic.md>), [cli](<https://devfeed.tech/tags/cli.md>), [export](<https://devfeed.tech/tags/export.md>), [http](<https://devfeed.tech/tags/http.md>), [json](<https://devfeed.tech/tags/json.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [search](<https://devfeed.tech/tags/search.md>), [service](<https://devfeed.tech/tags/service.md>), [socket](<https://devfeed.tech/tags/socket.md>), [spans](<https://devfeed.tech/tags/spans.md>), [traces](<https://devfeed.tech/tags/traces.md>), [unix](<https://devfeed.tech/tags/unix.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel Daemons can export OpenTelemetry spans to Vercel Tracing through a per-daemon Unix socket whose path is provided in `VERCEL_OTEL_SOCKET_PATH`. For Node.js daemons, `@vercel/otel` 2.3.0 or later automatically detects the socket with default configuration; initialize OpenTelemetry before the worker starts. The Vercel CLI can search traces by project and service name and return JSON, including daemon spans from the last hour.

## Source excerpt

Vercel Daemons can now send OpenTelemetry traces to Vercel Tracing, allowing you and your agents to inspect background worker operations alongside the rest of your project's traces. Vercel provides each daemon with a Unix socket for receiving OTLP/HTTP traces and sets the socket's path in VERCEL_OTEL_SOCKET_PATH. Upgrading @vercel/otel to version 2.3.0 or later enables automatic trace export for Node.js daemons using the default configuration. The SDK detects this socket and sends the spans your worker records to Vercel. These spans are available through the Vercel CLI, which can search by service name within a project and return JSON for your agents. Learn more in the daemon tracing documentation. Read more