ln-627-observability-auditor

Audit logging, health checks, metrics, and tracing in codebases.

Updated Mar 14, 2026

Search Tags:#logging #audit #metrics #observability #tracing #health-check #markdown-report

Ready to run

npx skills add https://github.com/0xtaoist/taogate --skill ln-627-observability-auditor-0xtaoist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-627-observability-auditor
Source: https://github.com/0xtaoist/taogate/tree/main/ln-627-observability-auditor
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-627-observability-auditor-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing observability patterns across a codebase to identify gaps in logging, health checks, metrics, and tracing, enabling teams to reach production-grade visibility.

Core Features & Use Cases

Structured logging validation: ensures logs include proper levels and structure for easy parsing.
Health endpoints verification: checks for standard endpoints like /health, /ready, and /live.
Metrics instrumentation discovery: detects metrics collection and relevant counters, histograms, and gauges.
Request tracing checks: validates trace propagation and correlation IDs across services.
Use Case: When upgrading to a distributed architecture, run this auditor to surface observability gaps and generate remediation guidance.

Quick Start

Run the observability auditor to generate the findings report for your project.

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 implementations across my microservices?▼

You can audit observability implementations by evaluating logging, health checks, metrics, and tracing to identify visibility gaps. This process validates structured logging, health endpoints, metrics collection, and request tracing across distributed architectures, outputting a detailed markdown report with findings and a score.

What is structured logging validation and how does it work for production services?▼

Structured logging validation ensures logs include proper levels and structures for easy parsing in production environments. It checks that web services and microservices implement appropriate log levels and formatting, enabling teams to reach production-grade visibility and generate actionable remediation guidance.

How do I check for health endpoints and metrics instrumentation in my codebase?▼

Checking for health endpoints and metrics instrumentation involves verifying standard endpoints like /health, /ready, and /live, while discovering metrics collection counters, histograms, and gauges. This validates that web services maintain proper health checks and metrics collection for production readiness.

Can I validate request tracing and correlation IDs across a distributed architecture?▼

Yes, you can validate request tracing and correlation IDs across distributed architectures. The validation checks trace propagation across services, ensuring distributed systems maintain proper request tracing and correlation ID implementation for comprehensive observability coverage.

Does this observability audit work for both monoliths and microservices?▼

Yes, the observability audit works for both monoliths and distributed microservices architectures in production. It evaluates logging, health checks, metrics, and tracing implementations regardless of architecture type, generating a detailed markdown report with findings and a score for any web service codebase.