logging-best-practices

Canonical log lines are single, context-rich wide events emitted per request per service. They improve observability by embedding user, request, and environment data for reliable end-to-end traceability and post-mortem analysis.

Implement middleware-based JSON logging by configuring a single logger to collect timing, status, and environment context. This middleware emits one wide event per request, enriching it with business context for queryable analytics.

Wide events provide high cardinality and dimensionality by including user, request, and environment data in a single output. This approach prevents fragmented logs, supporting deep queries and reliable cross-service transaction debugging.

Yes, this approach works for microservices by enforcing a consistent JSON schema across distributed services. Middleware-driven wide event collection ensures every request carries business and environment context for full traceability.

The best way to standardize logs is using a single logger with a JSON-based schema. Applying a reusable middleware pattern ensures consistent wide event collection, maintaining queryable formats across all services.

Include business context by configuring middleware to enrich each JSON wide event with user, request, and environment data. This high-dimensional logging approach captures the necessary details for deep post-mortem analysis.