audit-observability

Audit logging, metrics, tracing, and alerting coverage to produce a risk-ranked gaps report.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill audit-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-observability
Source: https://github.com/tomzx/agents/tree/main/skills/audit-observability
Command: npx skills add https://github.com/tomzx/agents --skill audit-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits production and development codebases to identify missing observability in logging, metrics, tracing, and alerting, enabling teams to prioritize instrumentation before issues affect users.

Core Features & Use Cases

  • Assess observability coverage across four pillars (logging, metrics, tracing, alerting) and generate a risk-ranked gaps report.
  • Support pre-production readiness reviews, post-incident follow-ups, and ongoing observability improvements by highlighting gaps and remediation steps.
  • Provide guidance for implementing instrumentation and alert configurations to meet SLOs.

Quick Start

Run the audit against your service directory to generate a prioritized gaps report.

Frequently Asked Questions about audit-observability

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

FAQPage Schema
How do I identify observability gaps in my production codebase?

Identify observability gaps by auditing your codebase across logging, metrics, tracing, and alerting to generate a risk-ranked report. This analysis requires access to your codebase and deployment environment to highlight missing instrumentation and guide remediation steps.

What is observability gap analysis and when do I need it?

Observability gap analysis assesses missing coverage across logging, metrics, tracing, and alerting to produce a risk-ranked report. You need it for pre-production readiness reviews, post-incident follow-ups, and ongoing improvements to ensure your service meets SLOs before issues affect users.

How do I audit tracing and alerting coverage for a live service?

Audit tracing and alerting coverage by applying gap analysis directly to your live service or repositories. The process evaluates existing instrumentation against clear criteria, prioritizing fixes based on risk to produce a targeted remediation report for your deployment environment.

Can I use observability gap analysis for pre-production readiness reviews?

Yes, you can use observability gap analysis for pre-production readiness reviews. It assesses instrumentation coverage across the four observability pillars, highlighting gaps and providing remediation steps to ensure your service meets SLOs before deployment.

What's the best way to prioritize missing instrumentation and alert configurations?

Prioritize missing instrumentation by generating a risk-ranked gaps report based on clear criteria. This approach evaluates logging, metrics, tracing, and alerting coverage, guiding remediation by focusing first on the highest-risk gaps that could impact users.

Do I need existing instrumentation to perform an observability audit?

The audit requires awareness of existing instrumentation but works even if coverage is incomplete. It evaluates available logging, metrics, tracing, and alerting across your codebase or live service to identify exactly what is missing and rank those gaps by risk.