sentry-nextjs-sdk

Sentry error monitoring and tracing in Next.js requires configuring three runtime files: instrumentation-client.ts, sentry.server.config.ts, and sentry.edge.config.ts. This captures errors and traces across client, server, and edge runtimes.

Yes, Sentry works with both the Next.js App Router and Pages Router. It provides automated error monitoring, distributed tracing, and session replay across app routes, API routes, and middleware for both routing paradigms.

You can monitor AI calls in Next.js using optional Sentry AI monitoring integrations. This provides end-to-end observability for operations using OpenAI, Vercel AI SDK, and Anthropic platforms.

Distributed tracing for Next.js server actions connects frontend and backend flows by linking user sessions to backend operations. This tracks errors and traces across the entire request lifecycle.

Yes, separate Sentry configurations are needed for Next.js edge and server runtimes. You create sentry.server.config.ts and sentry.edge.config.ts files to enable instrumentation across the three distinct runtimes.

Session replay works with Next.js error monitoring by capturing user interactions alongside errors. This optional feature deepens debugging by replaying frontend user sessions to identify root causes.