sentry-sdk-patterns

name	sentry-sdk-patterns
description	Best practices for using Sentry SDK in TypeScript and Python. Use when implementing structured error context with scopes, breadcrumb strategies, beforeSend/beforeBreadcrumb filtering, custom fingerprinting, user context, or performance span creation. Trigger: "sentry best practices", "sentry patterns", "sentry sdk usage", "sentry scope", "sentry breadcrumbs", "sentry beforeSend", "sentry fingerprint".
allowed-tools	Read, Write, Edit, Grep
version	1.51.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","sentry","python","typescript","best-practices","error-handling"]
compatibility	Designed for Claude Code

Sentry SDK Patterns

Overview

Production patterns for @sentry/node (v8+) and sentry-sdk (Python 2.x+) covering scoped error context, breadcrumb strategies, event filtering with beforeSend, custom fingerprinting for issue grouping, and performance instrumentation with spans. All examples use real Sentry SDK APIs.

Prerequisites

• Sentry SDK v8+ installed (@sentry/node, @sentry/react, or sentry-sdk)
• SENTRY_DSN environment variable configured
• Familiarity with async/await (TypeScript) or context managers (Python)

Instructions

Step 1 -- Structured Error Context with Scopes

Use Sentry.withScope() (TypeScript) or sentry_sdk.new_scope() (Python) to attach context to individual events without leaking state across requests.

TypeScript -- Scoped error capture:

import * as Sentry from '@sentry/node';

type ErrorSeverity = 'low' | 'medium' | 'high' | 'critical';

interface ErrorOptions {
  severity?: ErrorSeverity;
  tags?: Record<string, string>;
  context?: Record<string, unknown>;
  user?: { id: string; email?: string };
  fingerprint?: string[];
}

const SEVERITY_MAP: <, .> = {
  : ,
  : ,
  : ,
  : ,
};

  () {
  .( {
    scope.([options. || ]);

     (options.) {
      .(options.).( {
        scope.(key, value);
      });
    }
     (options.) {
      scope.(, options.);
    }
     (options.) {
      scope.(options.);
    }
     (options.) {
      scope.(options.);
    }

    .(error);
  });
}