sentry-and-otel-setup

Configure Sentry and OpenTelemetry error tracking and performance monitoring for Next.js applications.

6|Updated Nov 11, 2025

Search Tags:#observability #tracing #sentry #otel #error-monitoring

Ready to run

npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill sentry-and-otel-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sentry-and-otel-setup
Source: https://github.com/hopeoverture/worldbuilding-app-skills/tree/main/skills/development/sentry-and-otel-setup
Command: npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill sentry-and-otel-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Provides comprehensive error tracking and distributed tracing setup using Sentry and OpenTelemetry for Next.js apps.

Core Features & Use Cases

Install and configure Sentry for client/server/edge
Set up OpenTelemetry instrumentation and Sentry integration
Add custom logging, error boundaries, and middleware hooks
Templates for instrumentation, logging, and error handling

Quick Start

Run the wizard and copy templates to start integrating Sentry/OTel in your project.

Frequently Asked Questions about sentry-and-otel-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up error tracking and performance monitoring for my Next.js application?▼

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.

Can I use Sentry and OpenTelemetry together for distributed tracing?▼

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.

What's the best way to implement structured logging with context in a Next.js app?▼

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.

Do I need to instrument Server Actions and routes separately for tracing?▼

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.

How do I set up error boundaries and replay session support in Next.js?▼

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.

What are the limitations of OpenTelemetry integration with Sentry in edge environments?▼

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.