tracing

To establish distributed tracing in NestJS, use a global HTTP interceptor to create Sentry transactions and propagate trace headers across RabbitMQ, Kafka, and inter-service HTTP requests for end-to-end visibility.

AsyncLocalStorage maintains per-request session context in NestJS by storing data throughout the asynchronous call chain, enabling Winston logs and Sentry breadcrumbs to be enriched with unified trace insights without explicit parameter passing.

Yes, you can automatically create and chain Sentry spans for method executions by applying a decorator-driven tracing pattern, specifically using the @LogExecution decorator to instrument functions without manual span management.

The best way to correlate logs across NestJS microservices is using a Sentry Winston transport combined with AsyncLocalStorage, injecting trace IDs into logs and sending them as Sentry breadcrumbs for centralized debugging.

Yes, this observability approach supports inter-service messaging by extracting and propagating trace headers when publishing or consuming messages through RabbitMQ and Kafka, ensuring continuous distributed trace chains.