ln-627-observability-auditor

Audit observability patterns for logging, health checks, metrics, tracing, and log levels.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-627-observability-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-627-observability-auditor
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-627-observability-auditor
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-627-observability-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill audits observability patterns including structured logging, health checks, metrics, tracing, and log levels to improve monitoring capabilities.

Core Features & Use Cases

  • Validate structured logging and log levels
  • Ensure presence of health checks and basic metrics
  • Check trace propagation and OpenTelemetry/Zap patterns
  • Return findings with severity and recommended actions

Quick Start

Run ln-627-observability-auditor to assess observability readiness and receive actionable guidance.

Frequently Asked Questions about ln-627-observability-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit observability in my codebase for logging, metrics, and tracing?

Observability auditing checks structured logging, health endpoints, metrics instrumentation, and trace propagation to identify gaps. This Skill scans your codebase within CI/CD pipelines, flagging missing log levels, unstructured logs, absent health checks, and incomplete tracing setup, then scores compliance and recommends fixes.

What observability patterns should I validate before deploying to production?

Validate structured logging format, appropriate log levels, health check endpoints, basic metrics instrumentation, and request tracing propagation. These patterns ensure your system is monitorable; this Skill automates checking all five, reporting severity and effort for each gap found.

Can I check observability compliance as part of my CI/CD pipeline?

Yes. This Skill integrates into CI/CD pipelines using your tech stack and framework context to run observability checks automatically. It generates findings with severity levels, locations in code, remediation effort, and recommendations without manual inspection.

How do I know if my logging is structured and using correct log levels?

Structured logging validation checks that logs follow consistent, parseable formats and use appropriate severity levels (debug, info, warn, error). This Skill identifies unstructured or misleveled logs automatically, flagging them with recommendations to standardize.

What's the difference between health checks and metrics for observability?

Health checks signal service readiness through dedicated endpoints; metrics measure system behavior over time (requests, latency, errors). Both are essential—health checks enable fast failure detection, metrics enable trend analysis. This Skill ensures both are present and instrumented correctly.

Does this work with OpenTelemetry and Zap logging frameworks?

Yes. This Skill includes pattern checks for OpenTelemetry trace propagation and Zap structured logging. It validates your implementation against these frameworks within your codebase context and reports compliance gaps with actionable recommendations.