sre-monitoring-and-observability

Monitor system performance and generate SLIs, alerts, dashboards, and traces.

187|20|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/TheBushidoCollective/han --skill sre-monitoring-and-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-monitoring-and-observability
Source: https://github.com/TheBushidoCollective/han/tree/main/do/do-site-reliability-engineering/skills/sre-monitoring
Command: npx skills add https://github.com/TheBushidoCollective/han --skill sre-monitoring-and-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a framework for building comprehensive monitoring and observability systems, enabling you to quickly detect, diagnose, and resolve issues before they impact users. It automates the application of best practices for system visibility.

Core Features & Use Cases

  • Four Golden Signals: Monitor Latency, Traffic, Errors, and Saturation to understand system performance and user experience.
  • SLIs & Alerting: Define Service Level Indicators (SLIs) and configure effective alerts with severity levels, focusing on symptoms over causes.
  • Distributed Tracing & Structured Logging: Implement OpenTelemetry for end-to-end request visibility and structured logging for efficient log analysis.
  • Use Case: When a user reports slow performance, use this Skill to quickly check the Four Golden Signals on your dashboards, trace the request through distributed tracing, and analyze structured logs to pinpoint the exact bottleneck, reducing diagnostic time from hours to minutes.

Quick Start

Use the sre-monitoring-and-observability skill to define Prometheus queries for the Four Golden Signals for a new microservice.

Frequently Asked Questions about sre-monitoring-and-observability

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

FAQPage Schema
How do I monitor the four golden signals for system performance?

The four golden signals—latency, traffic, errors, and saturation—are key metrics that measure system health. Monitor these across microservices and endpoints using Prometheus-style metrics like http_request_duration_seconds and http_requests_total to detect performance issues before they impact users.

What's the best way to set up distributed tracing and structured logging?

Implement OpenTelemetry for end-to-end request tracing across services and structured logging for efficient log analysis. Together, they enable you to trace requests through your system and quickly pinpoint bottlenecks when diagnosing performance problems.

How do I define SLIs and configure alerting for my services?

Define Service Level Indicators (SLIs) based on the four golden signals, then configure alerts with severity levels focused on symptoms rather than causes. This approach enables proactive issue detection and faster incident response across your infrastructure.

Can I use this monitoring framework with microservices, REST endpoints, and background workers?

Yes, this framework applies across microservices, REST endpoints, batch jobs, and background workers. It collects latency, traffic, errors, and saturation signals uniformly, enabling consistent observability across your entire system architecture.

What observability outputs does this approach provide?

This framework generates SLIs, alerts, dashboards, and traces for end-to-end observability. It also produces RED/USE best-practice runbooks and incident response guidance, reducing diagnostic time from hours to minutes when issues occur.

Do I need Prometheus-style metrics and OpenTelemetry tracing together?

Both are complementary. Prometheus metrics provide aggregate signals about system behavior; OpenTelemetry tracing shows request flow through distributed systems. Using both gives you both breadth and depth needed for comprehensive observability.