How do I configure Sentry error tracking in a distributed NestJS backend to properly capture unhandled promise rejections without flooding our alert channels?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do I configure Sentry error tracking in a distributed NestJS backend to properly capture unhandled promise rejections without flooding our alert channels?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Sentry official NestJS setup Node SDK unhandled promise rejections integrations beforeSend sampling alerts grouping Google ↗
NestJS official exception filters unhandled promise rejection process event Node.js documentation Google ↗
- Sentry · docs.nestjs.com
- Exception filters · docs.nestjs.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Sentry official NestJS setup Node SDK unhandled promise rejections integrations beforeSend sampling alerts grouping OBSERVED | Google ↗ AI Mode ↗ | — | Reason | — | — | 1x of 1 | |
NestJS official exception filters unhandled promise rejection process event Node.js documentation OBSERVED | Google ↗ AI Mode ↗ | — | Reason | — | — | 1x of 1 |