Why are runbooks included in a monitoring skill?

Monitoring is only effective if it leads to resolution. This skill ensures every alert is paired with a 1-pager runbook to enable fast diagnosis and escalation.

What metrics does this monitoring strategy prioritize?

The skill focuses on key performance indicators including request latency (p50, p95, p99), error rates by type, throughput, and queue depth.

How does it handle Service Level Objectives (SLOs)?

It guides users to define specific objectives like '99.9% uptime' and then configures alerts to trigger specifically when those objectives are at risk of being missed.

How does this skill help with alert fatigue?

It provides standards-grounded guidance on setting data-driven thresholds and focusing on high-signal trend alerts rather than noisy absolute values that lead to on-call burnout.

Does this skill support modern observability standards?

Yes, it is grounded in industry standards like the Google SRE Book and 'Observability Engineering', covering the three pillars: metrics, logs, and traces.

Monitoring Strategy & Observability

Name: Monitoring Strategy & Observability
Author: sethdford

bysethdford

•

분석 및 모니터링

Designs high-signal monitoring and alerting systems to ensure production reliability while preventing alert fatigue.

This skill empowers tech leads to architect robust observability frameworks by defining Service Level Objectives (SLOs), selecting critical performance metrics, and establishing data-driven alert thresholds. Grounded in SRE best practices, it focuses on creating actionable, trend-based alerts paired with comprehensive runbooks. This approach streamlines incident response, reduces noise for on-call engineers, and provides deep visibility across metrics, logs, and traces to catch production issues before they impact customers.

주요 기능

01Data-driven threshold setting using historical variance and 3-sigma rules

02Critical metric selection including p95 latency and error rates

03Trend-based alerting to minimize false positives and alert fatigue

04Actionable runbook development for streamlined incident resolution

05Strategic SLO definition for performance and uptime tracking

065 GitHub stars

사용 사례

01Reducing alert fatigue for an overburdened on-call engineering team

02Establishing observability for a new microservice architecture

03Improving incident response times through structured, context-rich alerts

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add sethdford/claude-skills monitoring-strategy

For use in Claude.ai and ChatGPT

주요 기능

01Data-driven threshold setting using historical variance and 3-sigma rules

02Critical metric selection including p95 latency and error rates

03Trend-based alerting to minimize false positives and alert fatigue

04Actionable runbook development for streamlined incident resolution

05Strategic SLO definition for performance and uptime tracking

065 GitHub stars

사용 사례

01Reducing alert fatigue for an overburdened on-call engineering team

02Establishing observability for a new microservice architecture

03Improving incident response times through structured, context-rich alerts

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add sethdford/claude-skills monitoring-strategy

For use in Claude.ai and ChatGPT