# Cross-link map: Instrumentation (/docs/tracing/instrumentation)

> From the Vercel docs graph (built 2026-10-22T06:14:20.626Z), spanning vercel.com docs + KB, nextjs.org, ai-sdk.dev, and other Vercel documentation sites. Full graph as JSON: https://vercel.com/docs/graph.json

## Semantically closest pages

- [Tracing](https://vercel.com/docs/tracing) — Learn how to trace your application to understand performance and infrastructure details.
- [How to set up instrumentation with OpenTelemetry](https://nextjs.org/docs/app/guides/open-telemetry) — Learn how to instrument your Next.js app with OpenTelemetry.
- [How to instrument your Next.js app with OpenTelemetry](https://nextjs.org/docs/pages/guides/open-telemetry) — Learn how to instrument your Next.js app with OpenTelemetry.
- [OpenTelemetry](https://eve.dev/docs/observability/otel) — Configure OpenTelemetry destinations, content capture, and third-party exports.
- [Instrument and trace applications with the OpenTelemetry collector](https://vercel.com/changelog/instrument-and-trace-applications-with-the-opentelemetry-collector)

## Prerequisites

- [Tracing](https://vercel.com/docs/tracing) — Learn how to trace your application to understand performance and infrastructure details.

## This page links to (3)

- [How to set up instrumentation with OpenTelemetry](https://nextjs.org/docs/app/guides/open-telemetry) — Learn how to instrument your Next.js app with OpenTelemetry.
- [Trace Drains Reference](https://vercel.com/docs/drains/reference/traces) — Learn about Trace Drains - OpenTelemetry-compliant distributed tracing data formats and configuration.
- [Session tracing](https://vercel.com/docs/tracing/session-tracing) — Learn how to trace your sessions to understand performance and infrastructure details.

## Pages that link here (10)

By site: ai-sdk (1) · nextjs (4) · vercel-kb (2) · workflow (1) · vercel-docs (2)

### From ai-sdk

- [MLflow](https://ai-sdk.dev/providers/observability/mlflow) — Track, visualize, and debug Vercel AI SDK traces with MLflow Tracing

### From nextjs

- [How to set up instrumentation](https://nextjs.org/docs/app/guides/instrumentation) — Learn how to use instrumentation to run code at server startup in your Next.js app
- [How to set up instrumentation with OpenTelemetry](https://nextjs.org/docs/app/guides/open-telemetry) — Learn how to instrument your Next.js app with OpenTelemetry.
- [How to set up instrumentation](https://nextjs.org/docs/pages/guides/instrumentation) — Learn how to use instrumentation to run code at server startup in your Next.js app
- [How to instrument your Next.js app with OpenTelemetry](https://nextjs.org/docs/pages/guides/open-telemetry) — Learn how to instrument your Next.js app with OpenTelemetry.

### From vercel-kb

- [Add structured application logs to Vercel Functions](https://vercel.com/kb/guide/add-structured-application-logs-to-vercel-functions) — Learn how to add structured application logs to Vercel Functions to help troubleshoot function issues in real time.
- [Migrate self-hosted Next.js and containers from AWS to Vercel](https://vercel.com/kb/guide/migrate-containers-from-aws-to-vercel) — Migrate containers from AWS to Vercel: deploy with Dockerfile.vercel, keep RDS, S3, and SQS in AWS over OIDC, and cut ov

### From workflow

- [Tracing](https://workflow-sdk.dev/docs/observability/tracing) — Trace workflow execution end to end with OpenTelemetry.

### From vercel-docs

- [Tracing](https://vercel.com/docs/tracing) — Learn how to trace your application to understand performance and infrastructure details.
- [Always-on Tracing](https://vercel.com/docs/tracing/always-on-tracing) — Continuously collect traces from your production and preview traffic using sampling rules, so you can debug real request