How do you integrate a third-party error tracker like Sentry inside a global exception filter in NestJS?

Q: How do you integrate a third-party error tracker like Sentry inside a global exception filter in NestJS?

@Catch() export class SentryExceptionFilter implements ExceptionFilter { constructor( private readonly logger: LoggerService, @Inject(SENTRY_CLIENT) private readonly sentry: SentryClient, ) {} catch(exception: unknown, host: ArgumentsHost): void { const ctx = host.switchToHttp(); const req = ctx.getRequest (); const res = ctx.getResponse (); // Report to Sentry only for unexpected 5xx errors const isHttpException = exception instanceof HttpException; const is5xx = isHttpException && exception.getStatus() >= 500; if (!isHttpException || is5xx) { this.sentry.captureException(exception, { extra: { url: req.url, method: req.method, userId: (req as any).user?.id, }, }); } const status = isHttpException ? exception.getStatus() : 500; const message = isHttpException ? exception.message : 'Internal server error'; res.status(status).json({ statusCode: status, message }); } } Only send 5xx and unexpected errors to Sentry — 4xx client errors are expected and create noise. Include request URL, method, and authenticated user ID as extra context in Sentry events. Use APP_FILTER for registration so Sentry client and LoggerService are DI-injected. Never send raw exception stacks or database error details to the client even when tracking. Sentry.captureException() is fire-and-forget — always send the HTTP response before it completes.

Difficulty: 5/10

Exception Filters, Sentry Integration, NestJS Global Middleware

Register the filter via APP_FILTER so it can inject the Sentry client and any other services through the DI container. Only report unexpected server errors (5xx) to Sentry — not expected client 4xx errors. Include request context like URL, method, and user ID in the Sentry event for actionable error reports.

Global filter with Sentry integration

Error tracking integration best practices:

1
Only send 5xx and unexpected errors to Sentry — 4xx client errors are expected and create noise.
2

How do you integrate a third-party error tracker like Sentry inside a global exception filter in NestJS?

Difficulty: 5/10

Exception Filters, Sentry Integration, NestJS Global Middleware

Register the filter via APP_FILTER so it can inject the Sentry client and any other services through the DI container. Only report unexpected server errors (5xx) to Sentry — not expected client 4xx errors. Include request context like URL, method, and user ID in the Sentry event for actionable error reports.

Global filter with Sentry integration

Error tracking integration best practices:

1
Only send 5xx and unexpected errors to Sentry — 4xx client errors are expected and create noise.
2

How do you integrate a third-party error tracker like Sentry inside a global exception filter in NestJS?

How do you integrate a third-party error tracker like Sentry inside a global exception filter in NestJS?

Scenario Questions

Follow-up Questions