Collection prerequisites
Use this reference before setup or querying when collection is uncertain. Reuse completed setup.
Choose the spans needed
Infrastructure and outbound-fetch spans are automatic and need no application OpenTelemetry setup. Framework and custom spans need application instrumentation deployed to the target environment, except framework spans under Next.js 16.5+ default tracing. Library spans also need it, plus an opt-in for each installed library that has one. See automatic instrumentation.
Choose a collection mode
| Mode | Use for | Required setup |
|---|---|---|
| Always-on tracing | Investigating sampled traffic already captured | Matching positive sampling rules for the project, environment, and paths |
| Single request | Reproducing an endpoint from the terminal | CLI request capture against a deployment |
| Browser session or page | Reproducing a flow interactively | Browser capture with the Vercel Toolbar enabled |
Request and browser capture do not require always-on tracing rules. See session tracing.
Verify before querying
- Select the intended team, project, and preview or production deployment. Local execution alone is insufficient.
- For framework and custom spans, check that instrumentation is deployed. Under Next.js 16.5+ default tracing, framework spans need none unless Vercel skips adding
@vercel/otel; custom spans still do. - Check the selected mode's setup. For always-on tracing, inspect existing rules before an authorized change; see configuration.
- Send requests after collection is enabled. Query the same project, environment, and time window, then inspect a representative trace.
Use troubleshooting if the expected spans are absent.