monitoring

Define Golden Signals metrics and configure alerts for system monitoring.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/baphled/dotopencode --skill monitoring-baphled
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/baphled/dotopencode/tree/main/skills/monitoring
Command: npx skills add https://github.com/baphled/dotopencode --skill monitoring-baphled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring systems are observable and their health is continuously monitored, preventing downtime and performance degradation.

Core Features & Use Cases

  • Metric Definition: Helps define key metrics (SLIs) for system performance and reliability.
  • Alerting Strategy: Guides the setup of actionable alerts based on defined metrics and SLOs.
  • Dashboard Design: Assists in creating insightful dashboards for various stakeholders.
  • Use Case: When deploying a new microservice, use this Skill to define its Golden Signals (Latency, Traffic, Errors, Saturation) and set up alerts for critical thresholds.

Quick Start

Use the monitoring skill to define the four golden signals for a new web service.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I define the Four Golden Signals for a new microservice?

To define the Four Golden Signals, identify key metrics for Latency, Traffic, Errors, and Saturation. This establishes baseline system observability and tracks service health to prevent performance degradation after deployment.

What is the best way to set up actionable alerts for system monitoring?

Setting up actionable alerts requires defining Service Level Objectives and thresholds tied to specific metrics. This approach minimizes alert fatigue by triggering notifications only for critical system health issues requiring runbook intervention.

How do I create insightful dashboards for observability and health checks?

Create insightful dashboards by visualizing defined Service Level Indicators and key metrics tailored for various stakeholders. This provides real-time observability into system health, revealing performance bottlenecks and traffic patterns.

When do I need to implement continuous monitoring for post-deployment health?

You need continuous monitoring when deploying new microservices to prevent downtime and performance degradation. It ensures system observability by tracking key metrics and validating that the deployment meets reliability standards.

Can I use this approach to establish SLOs and SLIs for a new web service?

Yes, you can establish SLOs and SLIs by defining key metrics for service reliability and performance. This enables continuous monitoring and actionable alerting based on your specific web service thresholds.

Why does my alerting strategy need runbooks for observability?

Actionable alerting requires runbooks to provide operational context and resolution steps during incidents. This ensures system health issues are addressed quickly, preventing prolonged downtime and performance degradation.