logging-best-practices

From README

Logging Best Practices Skill Version: 1.0.0 Purpose 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. When to Apply Apply these guidelines when: Writing or reviewing logging code Adding console.log, logger.info, or similar Designing logging strategy for new services Setting up logging infrastructure Core Principles Wide Events (CRITICAL) 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. High Cardinality & Dimensionality (CRITICAL) Include fields with high cardinality (user IDs, request IDs - millions of unique values) and high dimensionality (many fields per event).