“Something failed” is not a useful production log.
Good logs should answer:
<ul>
<li>What happened?</li>
<li>Who triggered it?</li>
<li>Which request handled it?</li>
<li>Which entity was affected?</li>
<li>How long did it take?</li>
<li>What was the outcome?</li>
</ul>
Prefer structured logs with correlation IDs, actors, operations, entity IDs, durations and statuses.
Avoid logging complete request bodies. Passwords, tokens and payment details have a habit of becoming “temporary debugging information” forever.
Can your logs reconstruct one failed request from beginning to end?
#NestJS #Observability #Logging

Welcome to the NestJS Developers Hub, a collaborative community for developers passionate about NestJS! Whether you're a seasoned expert or just getting started, this group is dedicated to sharing knowledge, solving problems, and advancing our skills

Nestjs Developers

Structured logging best practices for production systems: good logs should capture what happened, who triggered it, request correlation IDs, affected entities, duration, and outcome. Advises against logging full request bodies since sensitive data like passwords and tokens tends to linger in debug logs.

Day 16/30 — Logs Must Tell a Story

Balancing between required logs and logging everything is tricky

Good logs save a lot of awkward incident archaeology