# Next.js already traces your requests. Here's how to export them with OpenTelemetry.

DevFeed: [Next.js already traces your requests. Here's how to export them with OpenTelemetry.](<https://devfeed.tech/articles/next-js-already-traces-your-requests-here-s-how-to-export-them-with-opentelemetry-24104.md>)

Original publisher: [Read original article](<https://blog.sentry.io/nextjs-export-traces-opentelemetry/>)

Author: Kyle Tryon

Published: 2026-06-29T09:00:00Z

Content type: tutorial

Language: en

Sources: [Sentry Blog](<https://devfeed.tech/sources/sentry-blog.md>)

Topics: [Next.js](<https://devfeed.tech/topics/next-js.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [next-js](<https://devfeed.tech/tags/next-js.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

This tutorial explains how to export the traces that Next.js generates automatically using OpenTelemetry and @vercel/otel. It covers sending traces to Sentry or other OTLP-compatible backends, understanding trace spans, and differences between Node and Edge runtimes.

## Source excerpt

Next.js creates OpenTelemetry traces automatically. Learn how to export them to Sentry or any OTLP backend with @vercel/otel.