logging

To prevent PII in Java logs, avoid logging personally identifiable information and full request or response bodies. Apply safety rules during code reviews to ensure log statements exclude sensitive data while maintaining debugging and observability capabilities.

Correct log levels map intent to severity: DEBUG for entry and exit points, INFO for business events, WARN for recoverable issues, and ERROR at exception boundaries. This mapping ensures logs remain meaningful and support effective monitoring.

Use SLF4J LoggerFactory with parameterized placeholders instead of string concatenation to create consistent log statements. This approach improves performance and ensures safe, structured logging across Java services, handlers, and libraries.

The best way to review logging consistency is to enforce rules during code reviews: verify correct SLF4J parameterized usage, validate appropriate log levels, and confirm no PII or full request bodies are logged. This ensures safe, meaningful logs.

Yes, this logging approach applies to Java services, handlers, and libraries. It enforces consistent, safe log statements using SLF4J LoggerFactory and parameterized placeholders across the codebase, ensuring observability without leaking private data.

Log stack traces at exception boundaries using the ERROR level. This ensures severe issues are captured for diagnosis while preventing noisy logs from lower-level recoverable issues, maintaining clear observability and consistent logging conventions.