devops/monitoring-alerting

Configure monitoring metrics, alert rules, and log management for production systems.

553|50|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/echoVic/boss-skill --skill devops-monitoring-alerting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops/monitoring-alerting
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/devops/monitoring-alerting
Command: npx skills add https://github.com/echoVic/boss-skill --skill devops-monitoring-alerting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack clear, consistent standards for what to monitor, when to alert, and how to manage logs, leading to missed incidents or alert fatigue. This Skill provides a structured reference for defining monitoring thresholds, alert severity levels, and log retention policies.

Core Features & Use Cases

  • Monitoring Metrics: Defines concrete thresholds for application metrics (error rate < 1%, P99 response time < 500ms) and system metrics (CPU < 80%, memory < 85%, disk < 90%).
  • Alert Rules: Maps severity levels P0-P3 to trigger conditions and notification channels, from phone calls for outages to email for resource warnings.
  • Log Management: Covers centralized log collection, log level classification (ERROR, WARN, INFO, DEBUG), 30-day retention, and sensitive data masking.
  • Use Case: When setting up observability for a new service, use this Skill to generate a complete monitoring and alerting baseline with thresholds and escalation paths.

Quick Start

Ask the agent to configure monitoring metrics and alert rules for your service using the monitoring-alerting guidelines.

Frequently Asked Questions about devops/monitoring-alerting

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

FAQPage Schema
How do I set up monitoring and alerting for a production service?

Define application metrics like error rate below 1% and P99 response time under 500ms, plus system metrics for CPU, memory, and disk. Then map alert severity levels P0 through P3 to conditions and notification channels such as phone, SMS, and email.

What alert severity levels should I use for incident response?

Use four levels: P0 for service unavailability with phone, SMS, and email notification; P1 for error rates above 5% via SMS and email; P2 for response times over 1 second via email; and P3 for resource usage above 80% via email.

What metrics should be monitored for application health?

Monitor application error rate with a threshold below 1% and P99 response time under 500ms. For system health, track CPU usage below 80%, memory usage below 85%, and disk usage below 90%.

How long should application logs be retained?

This guideline recommends a 30-day log retention policy combined with centralized log collection. Logs should be classified into ERROR, WARN, INFO, and DEBUG levels, with sensitive information masked before storage.

When should I use phone alerts versus email notifications?

Reserve phone calls combined with SMS and email for P0 incidents where the service is completely unavailable. Use email-only notifications for lower-severity issues like elevated response times or resource usage warnings to avoid alert fatigue.