monitoring-observability

Establish monitoring, metrics, alerting, and observability standards for software systems.

1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/komluk/scaffolding.template --skill monitoring-observability-komluk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/komluk/scaffolding.template/tree/main/stacks/_common/.claude/skills/monitoring-observability
Command: npx skills add https://github.com/komluk/scaffolding.template --skill monitoring-observability-komluk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides standards and best practices for monitoring, metrics, alerting, and observability, helping to ensure the health, performance, and reliability of systems.

Core Features & Use Cases

  • Observability Pillars: Understand and implement logs, metrics, and traces.
  • Key Metrics: Define and track essential metrics like latency, traffic, errors, and saturation using methods like RED and USE.
  • Alerting Strategy: Establish clear severity levels, rules, and actionable alerts to proactively address issues.
  • SLOs & SLIs: Define and monitor Service Level Indicators and Objectives to guarantee service quality.
  • Health Checks: Implement robust health check endpoints for liveness and readiness.
  • Use Case: When setting up a new microservice, use this Skill to define its key metrics, configure Prometheus alerts for high error rates, and establish an SLO for request latency.

Quick Start

Implement the four golden signals for the new user authentication service.

Frequently Asked Questions about monitoring-observability

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

FAQPage Schema
What are the three pillars of observability and how do they ensure system health?

Observability relies on logs, metrics, and traces to ensure system health. These pillars provide comprehensive visibility into application behavior, enabling proactive issue detection and reliable software performance monitoring.

How do I implement the four golden signals for monitoring a microservice?

To implement the four golden signals for monitoring a microservice, define and track latency, traffic, errors, and saturation. These metrics establish clear standards for evaluating system performance and detecting bottlenecks.

What is the difference between RED and USE metrics for tracking system performance?

RED metrics track Rate, Errors, and Duration for request-driven services, while USE metrics monitor Utilization, Saturation, and Errors for resource-based components. Both methods define key metrics to ensure system reliability.

How do I configure Prometheus alerts for high error rates using SLOs and SLIs?

Configure Prometheus alerts by defining Service Level Indicators (SLIs) and Service Level Objectives (SLOs) for error rates. Establish actionable alerting strategies with clear severity levels to proactively address system reliability issues.

When do I need distributed tracing and health checks for proactive issue detection?

Distributed tracing and health checks are needed when establishing comprehensive observability for microservices. Implement liveness and readiness endpoints alongside tracing to achieve proactive issue detection across complex software systems.

What is the best way to design dashboards and create runbooks for system reliability?

The best way to design dashboards and create runbooks is to align them with established SLOs and key metrics. This approach standardizes incident response, visualizes Golden Signals, and maintains system reliability.