observability

To set up distributed tracing and structured logging, you need to instrument your application code to emit consistent, queryable logs and trace requests across services. This skill provides patterns for instrumenting logs, metrics, and tracing to ensure end-to-end visibility using OpenTelemetry.

The best way to implement health checks and metrics collection is by exposing dedicated /health and /metrics endpoints in your service. This skill provides patterns for collecting metrics and setting up health endpoints to feed data into dashboards and alerting systems like Prometheus.

Yes, this observability skill works with OpenTelemetry, Sentry, and Prometheus. It provides structured patterns for metrics collection, distributed tracing, and error tracking using these specific tools to satisfy requirements for reliable monitoring and health checks.

You turn logs, metrics, and traces into actionable insight during incident response by correlating structured logs with distributed traces to visualize end-to-end request flows. This skill applies patterns across services to ensure reliable visibility and error tracking during incidents.

Yes, you can use this to add a minimal observability stack to an existing application by applying the provided patterns for structured logging, metrics, and tracing. It guides the setup of essential /health and /metrics endpoints to enable reliable monitoring.

You need distributed tracing when you must visualize end-to-end request flows across multiple services, whereas standard structured logging handles individual event queryability. This skill provides patterns for both to ensure comprehensive observability and reliable monitoring.