How to Build Unified Error Tracking Across HTTP, Cron, and Queue Boundaries in NestJS

A technical guide published on DEV Community outlines best practices for error tracking in production NestJS applications, particularly for logistics or agent-based systems. The core recommendation is to use a single shared error recorder that normalizes failures across HTTP, scheduled, and queue-driven execution boundaries, rather than relying solely on HTTP exception filters. Each boundary — HTTP interceptor, cron wrapper, or queue worker — should feed into this common recorder while preserving its own retry semantics. The guide stresses that error tracking must also capture cost attribution data, including tenant identifiers, workflow IDs, and accumulated usage, since a stack trace alone does not reveal which customer or process consumed resources. It also advises applying consistent redaction policies before any telemetry data reaches external sinks to avoid exposing raw customer information.