Overview
Vercel records a lot about every request: function and build logs, CDN and firewall decisions, its own spans, Web Vitals and page views. It keeps that data for a limited time (runtime logs for one day on Pro, 30 days with Observability Plus), and it can’t receive telemetry from services that run elsewhere. Data leaves Vercel in two ways:- Drains forward what Vercel’s platform records. The Marketplace connector creates them for every project in one step.
- OpenTelemetry from your code sends your own spans, with no drain fee. See OpenTelemetry in Vercel Functions.
Source-to-Method Mapping
The Marketplace connector creates the log, trace, Speed Insights and Web Analytics drains in one step, so for most sources it’s all you need. Each source links to a short page on what it emits and where to start.Ingestion Methods
- Marketplace connector: creates log, trace, Speed Insights and Web Analytics drains for every project in a team.
- Vercel Drains: what each drain sends, what it costs, how to create and filter drains yourself, and what happens when deliveries fail.
- OpenTelemetry in Vercel Functions: spans from your own code with
@vercel/otelor eve, without a drain fee. - Tracing into other services: one trace from a Vercel function into an API, proxy and database elsewhere.
- Deployment webhooks: deploy events with commit, branch and author, as markers next to your logs.