observability

Design distributed tracing and structured events by creating an observability strategy that defines concrete outputs like instrumentation guides and telemetry pipeline diagrams. This approach reveals system health and enables deep understanding without requiring disruptive code changes.

Implement OpenTelemetry instrumentation by following a generated instrumentation guide that defines structured events and tracing strategies. This enables comprehensive telemetry pipeline construction to improve diagnosis and reduce mean time to recovery across services.

Set up SLO-based alerting by defining concrete SLO definitions and sampling strategies within an observability design document. This targets service reliability improvements and provides structured alerts based on system health metrics.

Yes, you can assess observability maturity without code changes by evaluating current telemetry pipelines and instrumentation. The skill generates maturity assessments that outline structured event designs and distributed tracing upgrades for existing services.

Start building a telemetry pipeline by identifying target services, required OpenTelemetry instrumentation, and first-pass SLOs. This initial observability design outlines the structured events and distributed tracing needed for the new project.

Upgrade existing instrumentation when you need to improve diagnosis and mean time to recovery across services. Upgrading involves implementing structured event design, distributed tracing, and sampling strategies to achieve a higher observability maturity.