observability-patterns

SLI/SLO design starts by defining measurable reliability targets for your service using metrics like latency, error rate, and availability. This Skill provides canonical patterns for setting SLIs aligned with user experience and SLOs that specify acceptable thresholds, enabling data-driven reliability management across microservices and cloud-native systems.

Observability patterns unify logs, metrics, and traces as three interdependent pillars for system visibility. This Skill covers standardized schemas like RED and USE metrics, trace-context propagation, and structured logging to ensure correlation across all three signals, reducing mean time to resolution during incidents.

Alert noise reduction combines threshold tuning, anomaly detection, and correlation rules to surface only actionable signals. This Skill provides alerting strategies and templates that filter false positives while preserving coverage, enabling on-call teams to respond faster to real incidents in distributed systems.

Yes. This Skill delivers blueprint-driven dashboards and metric schemas that work across diverse technologies and platforms. By standardizing on RED/USE patterns and trace-context protocols, you can monitor heterogeneous microservices and cloud-native architectures with consistent instrumentation.

Effective incident response requires integrated monitoring that surfaces metrics, logs, and traces in real time. This Skill specifies monitoring infrastructure design including alerting, dashboards, and SLO configuration that enable teams to detect anomalies, correlate signals, and respond rapidly to production issues.

Trace-context propagation embeds correlation IDs and metadata in request headers to link spans across service boundaries. This Skill provides patterns for instrumenting trace collection across microservices, enabling end-to-end visibility into request flows and dependency chains for troubleshooting.