observability-analyst

To audit microservice observability, you validate the presence and functionality of critical health, readiness, metrics, and version endpoints. This ensures your services are thoroughly monitored, debugged, and alerted on in production environments.

Distributed tracing tracks requests across microservices, and auditing it assesses implementation and error handling strategies. A proper audit ensures correlation ID propagation is functional and validates PII protection within structured logs and traces.

Documenting Prometheus metrics involves reviewing existing metric practices and structured logging for completeness and adherence to standards. This process verifies that uptime monitoring, performance tracking, and incident response meet required observability baselines.

Yes, you can verify SLI and SLO dashboard adherence before a service goes live. The audit validates that observability stacks, including health endpoints and metrics, meet company standards for uptime monitoring and incident response.

Yes, observability auditing requires correlation ID propagation across microservices. Validating this propagation is a core component of assessing distributed tracing implementation and ensuring logs can be accurately traced throughout the system.

An observability stack fails to alert properly when health, readiness, and metrics endpoints are missing or misconfigured. Auditing these endpoints and validating Prometheus metrics ensures complete coverage for production incident response.