logging-best-practices

Version: 1.0.0 This skill provides guidelines for implementing effective logging in applications. It focuses on wide events (also called canonical log lines) - a pattern where you emit a single, context-rich event per request per service, enabling powerful debugging and analytics. Apply these guidelines when: Emit one context-rich event per request per service . Instead of scattering log lines throughout your handler, consolidate everything into a single structured event emitted at request completion. Include fields with high cardinality (user IDs, request IDs - millions of unique values) and high dimensionality (many fields per event). This enables querying by specific users and answering questions you haven't anticipated yet. Always include business context: user subscription tier, cart value, feature flags, account age. The goal is to know "a premium customer couldn't complete a $2,499 purchase" not just "checkout failed." Include environment and deployment info in every event: commit hash, service version, region, instance ID.