observability-checker

What problem does it solve?

Production services often lack complete, conformant observability, leaving teams unable to diagnose outages, latency regressions, or errors without redeploying, leading to extended mean time to resolution and end-user impact.

Core Features & Use Cases

• Four-pillar validation: Checks traces, metrics, logs, and continuous profiling for completeness, OpenTelemetry semantic convention conformance, and cross-pillar correlation via trace IDs.
• Risk detection: Flags high-cardinality metric labels that cause memory bombs, PII/secrets in logs, missing SLO/error budget definitions, and absent health/readiness probes.
• Use Case: A team preparing to launch a new payment microservice can run this skill to verify all HTTP, database, and queue boundaries are instrumented with OTel spans, logs carry trace context, and latency/availability SLOs are defined before release.

Quick Start

Use the observability-checker skill to audit your payment microservice's observability setup for missing trace instrumentation, unstructured logs, high-cardinality metrics, and undefined SLOs.