sentry-and-otel-setup

Error tracking and performance monitoring in Next.js requires installing Sentry and configuring OpenTelemetry instrumentation across client, server, and edge runtimes. This Skill provides configuration templates and setup steps to capture errors automatically, trace requests across boundaries, and instrument performance metrics end-to-end.

Yes. Sentry integrates with OpenTelemetry to enable distributed tracing across server and client boundaries. OpenTelemetry collects spans and metrics, while Sentry captures errors and replays sessions, giving you unified observability for debugging production issues.

Structured logging with contextual data is implemented by adding logging wrappers that capture request context and span information. This Skill includes templates for middleware hooks and custom logging that integrates with Sentry and OpenTelemetry to provide correlated logs across your application.

Server Actions and routes require separate instrumentation to capture their execution within your trace. This Skill includes specific patterns for instrumenting both, ensuring performance metrics and error context flow through your application's server-side logic.

Error boundaries catch React rendering errors on the client, while session replay captures user interactions before an error occurs. This Skill provides templates for implementing error boundaries and configuring Sentry's replay feature to aid debugging.

Edge environments have constrained runtime capabilities that may limit the span depth and metric resolution available compared to Node.js server environments. This Skill covers configuration patterns for edge runtimes while maintaining observability within those constraints.