Sentry

When to Use

• Adding error tracking or performance monitoring to React or NestJS
• Wrapping components or routes with error boundaries
• Enriching error reports with user context, tags, or breadcrumbs
• Configuring sampling rates, filtering, or source maps

When NOT to use:

• Structured logging (use a logger like Pino/Winston — Sentry is for exceptions, not log aggregation)
• Business analytics or user behavior tracking — use a product analytics tool
• Health check endpoints or expected 4xx responses — these are not errors

Our Conventions