observability-patterns

Design observability patterns for monitoring, tracing, logging, and SLOs.

381|48|Updated Aug 12, 2025

Search Tags:#logs #metrics #observability #traces #SLI

Ready to run

npx skills add https://github.com/rsmdt/the-startup --skill observability-patterns-rsmdt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-patterns
Source: https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/infrastructure/observability-patterns
Command: npx skills add https://github.com/rsmdt/the-startup --skill observability-patterns-rsmdt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides patterns for monitoring, tracing, logging, and SLO/SLI design to improve production reliability.

Core Features & Use Cases

Three pillars: Metrics, logs, traces and their interplay.
SLI/SLO design: Define service reliability targets.
Alerting strategies: Noise-reduced, signal-rich alerts.

Quick Start

Define an SLI for a payment API and sketch a corresponding alert rule.

Frequently Asked Questions about observability-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design SLIs and SLOs for microservices?▼

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.

What's the best way to structure logs, metrics, and traces together?▼

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.

How do I reduce alert noise while keeping signal-rich alerts?▼

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.

Can I apply observability patterns across different tech stacks?▼

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.

What monitoring infrastructure do I need for incident response?▼

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.

How do I propagate trace context across distributed services?▼

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.