Skip to content
Docs

Trace Drains Reference

Trace Drains forward distributed tracing data from your deployments to external endpoints for storage and analysis. You can configure Trace Drains in two ways:

Trace Drains use the OTLP/HTTP protocol exclusively. OTLP/gRPC endpoints (typically port 4317) are not supported. Make sure your endpoint accepts OTLP/HTTP requests (typically port 4318, path /v1/traces).

Vercel sends traces to endpoints over HTTPS following the OTLP/HTTP specification.

Trace Drains follow the OpenTelemetry traces specification. Vercel automatically adds these specific resource attributes to all traces:

NameTypeDescriptionExample
vercel.owner_idstringIdentifier for the Vercel team"team_a1b2c3d4e5f6g7"
vercel.project_idstringIdentifier for the Vercel project"prj_a1b2c3d4e5f6g7"
vercel.deployment_idstringIdentifier for the Vercel deployment"dpl_a1b2c3d4e5f6g7"

Trace Drains also send these values under the deprecated camelCase keys vercel.ownerId, vercel.projectId, and vercel.deploymentId. The next major version of the Trace Drains schema removes them. Read the snake_case keys instead.

Vercel supports the following formats for Trace Drains. You can configure the format when configuring the Drain destination:

Vercel sends traces as JSON objects following the OpenTelemetry specification:

{ "resourceSpans": [{ "resource": { "attributes": [{ "key": "service.name", "value": { "stringValue": "vercel-function" } }] }, "scopeSpans": [{ "scope": { "name": "vercel" }, "spans": [{ "traceId": "7bba9f33312b3dbb8b2c2c62bb7abe2d", "spanId": "086e83747d0e381e", "name": "GET /api/users", "kind": "server", "startTimeUnixNano": "1694723400000000000", "endTimeUnixNano": "1694723400150000000" }] }] }] }

Vercel sends traces in binary protobuf format over OTLP/HTTP. This format is more efficient for high-volume trace data transmission.

Sampling rules control how much trace data each drain forwards so you can manage observability depth and spend. Add sampling rules to define how much data reaches your destination:

  1. If no rules exist, click Add Sampling Rule.
  2. Choose the environment you want to sample from.
  3. Set the sampling percentage.
  4. (Optional) Specify a request path prefix. Leave it blank to apply the rule to every path.

Example workflows:

  • Launch-day monitoring: sample 100% of production traffic when you launch a new feature, then decrease to 10% once traffic stabilizes.
  • Static coverage: always collect 5% from /docs so you can spot regressions on a static documentation site.

Rules run from top to bottom. Requests that match a rule use that rule’s sampling rate, and any other requests are dropped. If you do not add rules, the drain forwards 100% of data to the destination.

For how sampling decisions are made, including per-trace hashing and rule precedence, see Sampling.

Trace Drains follow the shared attribute truncation behavior.

Trace Drains follow the shared Tracing limitations.

For more information on Trace Drains and how to use them, check out the following resources:

Last updated August 21, 2026

Was this helpful?

supported.