observability-monitoring

Audit Prometheus alert rules using the RED method.

140|23|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/AnastasiyaW/codex-claude-code-config --skill observability-monitoring-anastasiyaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-monitoring
Source: https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/observability-monitoring
Command: npx skills add https://github.com/AnastasiyaW/codex-claude-code-config --skill observability-monitoring-anastasiyaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the gap between vague system health questions and evidence-backed operational reality by providing a structured framework for monitoring, alerting, and incident response.

Core Features & Use Cases

  • Evidence-Based Monitoring: Implements the USE (Utilization, Saturation, Errors) and RED (Rate, Errors, Duration) methods to ensure monitoring covers both infrastructure and user-facing outcomes.
  • Incident Workflow: Provides a standardized triage process for live incidents, ensuring blast radius containment and proper evidence collection before any system mutation.
  • SLO/SLI Management: Guides the definition of Service Level Indicators and Objectives to prevent alert fatigue and ensure alerts are actionable and tied to business impact.

Quick Start

Use the observability-monitoring skill to audit my current Prometheus alert rules and suggest improvements based on the RED method.

Frequently Asked Questions about observability-monitoring

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

FAQPage Schema
How do I audit Prometheus alert rules to reduce alert fatigue?

You can audit Prometheus alert rules by applying SRE frameworks like RED and SLI/SLO to ensure alerts are actionable and tied to business impact, preventing alert fatigue.

What is the best way to structure incident response workflows for distributed systems?

Structuring incident response for distributed systems requires a standardized triage process ensuring blast radius containment and proper evidence collection before any system mutation.

How do USE and RED methods differ when monitoring service health?

The USE method monitors infrastructure health through Utilization, Saturation, and Errors, while the RED method tracks user-facing outcomes via Rate, Errors, and Duration.

Can I correlate metrics, logs, and traces using OpenTelemetry and Grafana?

Yes, you can correlate metrics, logs, and traces by integrating observability stacks like OpenTelemetry and Grafana to produce actionable diagnostics across distributed systems.

How do I define Service Level Indicators to prevent alert fatigue?

Defining Service Level Indicators requires mapping user-facing outcomes to SLO frameworks, ensuring generated alerts remain actionable and directly tied to business impact.

Why does incident triage require evidence collection before system mutation?

Incident triage requires evidence collection before system mutation to accurately assess the blast radius and prevent further degradation while diagnosing issues across distributed systems.