sentry-error-capture

# Sentry Error Capture ## Overview Capture errors and enrich them with structured context so your team can diagnose production issues in seconds instead of hours. Covers `captureException`, `captureMessage`, scoped context (`withScope` / `push_scope`), breadcrumbs, custom fingerprinting, and `beforeSend` filtering using `@sentry/node` v8 and `sentry-sdk` v2 APIs. ## Prerequisites - Sentry SDK installed and initialized (`@sentry/node` v8+ or `sentry-sdk` v2+) - A valid DSN configured via environment variable (`SENTRY_DSN`) - Understanding of try/catch (JS) or try/except (Python) error handling - A Sentry project created at [sentry.io](https://sentry.io) ## Instructions ### Step 1 -- Capture Exceptions with Full Stack Traces Always pass real `Error` objects (or Python exception instances), never plain strings. Plain strings lose the stack trace, making debugging far harder. **TypeScript (`@sentry/node`)** ```typescript import * as Sentry from '@sentry/node'; // CORRECT -- full stack trace preserved try { await riskyOperation(); } catch (error) { Sentry.captureException(error); } // WRONG -- no stack trace, hard to debug Sentry.captureException('something went wrong'); // Wrapping non-Error values into proper Error objects Sentry.captureException(new Error(`API returned ${statusCode}: ${body}`)); // Capture with inline context (no scope needed for simple cases) Sentry.captureException(error, { tags: { transaction: 'purchase' }, extra: { orderId, amount }, })...