What problem does it solve? Applications often emit unstructured, inconsistent logs that leak secrets, swallow stack traces, or drown signal in noise, making production incidents hard to trace and debug. ## Core Features & Use Cases - Structured JSON Logging Rules: Mandates JSON-to-stdout logs with required fields like timestamp, level, service, env, and message, plus parameterized logging instead of string concatenation. - Correlation ID Propagation: Binds correlation IDs into the log context (MDC) from inbound headers and forwards them on outbound HTTP calls and Kafka messages for end-to-end tracing. - Security Guardrails: Prohibits logging passwords, tokens, PII, and full request/response bodies, and defines deliberate log-level usage (DEBUG/INFO/WARN/ERROR). - Use Case: When implementing a Spring Boot service, apply these rules to add a CorrelationIdFilter, emit parameterized log statements with kv() pairs, and log exceptions once at ERROR with full stack traces. ## Quick Start Apply the logging-observability rules to review my service's logging code and rewrite it to use structured parameterized logs with correlation ID propagation.
