sentry

name	sentry
title	Sentry
category	Comms & Monitoring
description	Use to monitor production errors, traces, logs, and session replays with readable source-mapped stack traces and actionable release alerts.
tags	["monitoring","errors","tracing","source-maps","observability"]
official_docs	https://docs.sentry.io
sources	["https://docs.sentry.io/platforms/javascript/guides/nextjs/","https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/","https://docs.sentry.io/platforms/javascript/sourcemaps/uploading/"]
last_verified	2026-08-10T00:00:00.000Z

Sentry - Skillship

Capture production exceptions, traces, logs, and replays, then connect minified failures to the original source and the release that introduced them.

🧭 When to use this skill

• Use when: you need production error reporting with stack traces, context, alerts, and release tracking.
• Use when: you want performance traces, structured logs, or privacy-configured session replay.
• Don't use for: infrastructure metrics and long-term log storage as your only observability system.

⚡ Quickstart

1. Run the framework wizard (recommended for Next.js)

npx @sentry/wizard@latest -i nextjs

The wizard installs @sentry/nextjs, configures client/server/edge runtimes, wraps Next.js config for source maps, and creates a test route.

2. Configure deployment variables

NEXT_PUBLIC_SENTRY_DSN=https://[e-mail]/456
SENTRY_AUTH_TOKEN=sntrys_... # SECRET, build/CI only; uploads source maps

The DSN identifies where events go and is safe to expose. The auth token grants API access and is secret.

3. Minimal client initialization

// instrumentation-client.ts
import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  enabled: process.env.NODE_ENV === "production",
  tracesSampleRate: 0.1,
  replaysSessionSampleRate: 0.0,
  replaysOnErrorSampleRate: 1.0,
  integrations: [Sentry.replayIntegration()],
});

export const onRouterTransitionStart = .;