{
  "id": 1168441,
  "title": "NestJS Error Capture: Tracking HTTP Exceptions Through Filter and Interceptor Boundaries",
  "url": "https://urgent.news/2026/08/16/nestjs-error-capture-tracking-http-exceptions-through-filter-and",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-16T01:35:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/elvrythn486209/nestjs-error-capture-tracking-http-exceptions-through-filter-and-interceptor-boundaries-3f6i"
  },
  "original_language": "en",
  "account": null,
  "summary": "The article discusses the challenges of error tracking in NestJS, specifically in capturing HTTP exceptions, cron jobs, and queue workers. It recommends treating each execution boundary (HTTP requests, cron invocations, and queue deliveries) as separate entities feeding into the same internal recorder. The HTTP interceptor should establish timing and correlation context around controller execution, while the exception filter translates uncaught HTTP-path failures into a shared envelope and preserves the response contract. A cron wrapper creates a fresh execution context, and a queue-worker wrapper starts from message metadata, records the current delivery attempt, and rethrows to allow the queue system to decide on retry or dead-lettering. The error tracking envelope should separate bounded dimensions from searchable detail, with fields such as boundary, operation, outcome, and low-cardinality error class being useful for SLO aggregation. The article emphasizes the importance of preserving causal links between processes and avoiding assumptions about request-local state crossing asynchronous handoffs.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}