ring:dev-sre

You validate observability by auditing implementations for structured JSON logging, OpenTelemetry tracing, and context propagation. This skill checks that your code meets Ring standards, requiring timestamps, levels, and trace_ids for end-to-end correlation across handlers and services.

Context propagation validation works for HTTP and GRPC external calls by verifying that trace context is correctly propagated across service boundaries. It ensures distributed traces remain intact when your handlers, services, or repositories interact with external dependencies.

You enforce instrumentation coverage by running a validation audit that requires at least 90% instrumentation across your codebase. This gate validation verifies distributed traces are properly applied to handlers, services, and repositories before progressing to the testing phase.

Observability validation supports Go, TypeScript, and Python across service types including API, worker, batch, CLI, and library. It applies Ring standards uniformly to verify structured logging, tracing, and propagation compliance regardless of the language or service architecture.

When validation fails, the skill dispatches fixes to the implementation agent and re-validates up to three iterations. It reports a validation summary, instrumentation coverage percentage, and specific issues to resolve before moving to the next gate.

You need observability validation after implementing tracing and logging in Gate 0 and before testing in Gate 3. This Gate 2 validation step ensures your structured JSON logs and OpenTelemetry traces meet compliance requirements before progressing downstream.