monitoring-guidelines

Define monitoring requirements for metrics, alerting, SLOs, dashboards, and incident response.

1|Updated Feb 5, 2026

Search Tags:#monitoring #dashboards #metrics #observability #alerting #SLO #incident-response

Ready to run

npx skills add https://github.com/allthingslinux/atl.services --skill monitoring-guidelines

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: monitoring-guidelines
Source: https://github.com/allthingslinux/atl.services/tree/main/.agents/skills/monitoring-guidelines
Command: npx skills add https://github.com/allthingslinux/atl.services --skill monitoring-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitoring is essential for reliability and performance, providing visibility and proactive issue detection across applications and infrastructure.

Core Features & Use Cases

Core Monitoring Principles: latency, traffic, errors, saturation, and SLO-based alerting.
Alerting & Incident Response: define alerts, runbooks, and post-incident reviews.
Dashboards & Observability: unified dashboards and metrics storage for services and infrastructure.

Quick Start

Start by defining SLOs for critical services, instrument the four golden signals, set up dashboards and alert rules, and establish runbooks for incident response.

Frequently Asked Questions about monitoring-guidelines

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

FAQPage Schema

What metrics should I monitor for reliable application and infrastructure performance?▼

To monitor for reliable performance, track the four golden signals: latency, traffic, errors, and saturation. These core metrics provide essential visibility and proactive issue detection across your software and infrastructure.

How do I set up SLO-based alerting and incident response?▼

Set up SLO-based alerting by defining service level objectives for critical services, then configuring alert rules and establishing runbooks for incident response. This ensures proactive issue detection and structured post-incident reviews.

What's the best way to design dashboards for observability and metrics storage?▼

Design observability dashboards by creating unified views for services and infrastructure metrics. This provides clear visibility into system health and supports proactive capacity planning for your applications.

When do I need structured monitoring guidelines for my software systems?▼

You need structured monitoring guidelines when you want to improve reliability and visibility across software, infrastructure, and business contexts. They specify actionable requirements for metrics collection, alert configurations, and capacity planning.

How do I start building a reliable monitoring system from scratch?▼

Start by defining SLOs for critical services, instrumenting the four golden signals, setting up dashboards and alert rules, and establishing runbooks for incident response. This ensures clear visibility and proactive issue detection.