Daemons can now send traces to Vercel Tracing

Vercel has introduced support for sending OpenTelemetry traces from daemons to Vercel Tracing, integrating background worker operations into the existing trace visibility for projects. Each daemon receives a Unix socket configured to receive OTLP/HTTP traces, with the socket path set via the environment variable VERCEL_OTEL_SOCKET_PATH. This setup ensures traces generated by workers are automatically exported when using @vercel/otel version 2.3.0 or later, provided OpenTelemetry is initialized before the worker starts.

The integration simplifies trace collection by automatically detecting the Unix socket and forwarding spans recorded by workers to Vercel Tracing. This eliminates the need for manual configuration, allowing developers to focus on analyzing traces rather than setting up instrumentation. The traces are then accessible through the Vercel CLI, which supports searching by service name within a project and returning results in JSON format for further processing by agents.

Developers can query daemon spans from the last hour directly via the Vercel CLI, enabling quick inspection of background task performance and debugging. The CLI’s search functionality returns structured JSON output, making it easier to integrate trace data into monitoring tools or agent workflows. This feature is particularly useful for projects relying on long-running or periodic background processes.

Vercel provides curated documentation, guides, templates, and courses to assist developers in implementing this tracing capability. The resources cover stack selection, architectural decisions, and practical steps for building or extending applications and agents with trace-aware workflows. Ready-to-use prompts are also available to help coding agents leverage trace data effectively.