What problem does it solve?
Validates that developers implemented observability correctly so services are not blind in production. It detects missing structured JSON logs, absent or incomplete OpenTelemetry tracing, improper context propagation for external calls, and forbidden plain-print logging patterns that break monitoring and incident response.
Core Features & Use Cases
- Forbidden Pattern Detection: Identifies fmt.Println, console.log, and other non-structured logging usages and marks them as critical failures.
- Instrumentation Coverage Measurement: Counts spans across handlers, services, and repositories and enforces a minimum of 90% coverage with a tabular report.
- Context Propagation Checks: Verifies HTTP, gRPC, and queue calls inject tracing context so traces correlate across services.
- Automated Fix Workflow: Dispatches fixes to the implementation agent, re-validates up to three iterations, and escalates to the user if unresolved.
- Use case examples include Gate 2 validation for API services, background workers, and CI gating before testing.
Quick Start
Run the dev-sre skill to validate that task-001's Go API implementation includes JSON structured logging with trace_id, OpenTelemetry spans covering handlers/services/repositories, proper context propagation for external calls, and no forbidden console or fmt prints.
