review-observability

To audit observability gaps, evaluate logging, metrics, and tracing coverage against OpenTelemetry, Prometheus, and structured logging frameworks. This generates prioritized, code-referenced findings with impact assessments and effort estimates to reduce mean time to resolve.

Common observability gaps include missing trace propagation across RPCs, high-cardinality metric labels, and insufficient structured logging. Identifying these issues through a codebase audit provides prioritized, code-referenced findings aligned with industry best practices to reduce incident resolution time.

Yes, you can apply this observability audit to post-outage reviews and pre-release readiness checks. It assesses services using OpenTelemetry, Prometheus, or structured logging frameworks, returning grouped findings with code-level references and effort estimates to improve oncall experience.

OpenTelemetry tracing coverage should be checked alongside Prometheus metrics and structured logging. Evaluating correlation across these pillars ensures reliable production debugging by providing prioritized, code-referenced findings aligned with industry observability best practices.

The best way to identify missing trace propagation across RPCs is performing a structured observability audit. This evaluates tracing implementations against OpenTelemetry best practices, returning grouped findings with code-level references and effort estimates to resolve production incidents faster.