ln-627-observability-auditor

To audit observability practices, you can run a script-based analyzer against your codebase to detect deviations in structured logging, health checks, metrics, and tracing. It generates a detailed report with severity levels and effort estimations for identified gaps.

Structured logging uses specialized logging frameworks to output machine-readable data formats like JSON, unlike simple console.log statements. Auditing your codebase helps identify instances where console.log is used instead of structured logging, which is critical for effective monitoring and debugging.

Verifying health check endpoints involves scanning your codebase for essential routes like /health, /ready, or /live. This Skill checks for the presence of these endpoints to ensure your microservice meets standard observability and deployment readiness requirements.

Yes, the observability audit assesses both log levels and request tracing. It verifies that appropriate log levels are utilized for visibility and checks for the implementation of request tracing to ensure critical system interactions are properly monitored and debuggable.

Yes, you can use this observability audit for a microservice before deployment. It is designed to check if a new service meets company observability standards by generating a compliance report that highlights areas for improvement before the code goes live.