logging-best-practices

Wide events, or canonical log lines, improve observability by emitting a single, context-rich JSON log per request per service, capturing complete business and environment context to simplify debugging.

Implement structured logging by using a single startup logger with middleware to automatically generate and emit wide events in a unified JSON format, ensuring request correlation across APIs and background tasks.

Yes, middleware-based wide event logging works for distributed systems by automatically emitting one structured JSON event per request per service, including high-cardinality fields and business context for improved debuggability.

The best way to capture business context in microservices logs is adopting the wide events pattern, which uses middleware to bundle high-cardinality fields and environment metadata into a single end-of-request JSON event.

Common structured logging anti-patterns include creating noisy, unstructured logs and scattering context across multiple lines, which this Skill avoids by enforcing a single, context-rich JSON wide event per request.