monitoring

Diagnose CloudWatch alarms, metrics, and observability gaps across AWS services.

3|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/LiboMa/agenticops-chat --skill monitoring-liboma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/LiboMa/agenticops-chat/tree/main/skills/monitoring
Command: npx skills add https://github.com/LiboMa/agenticops-chat --skill monitoring-liboma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Cloud operations teams struggle with noisy alarms, missing metrics, and unclear thresholds across AWS services. This Skill provides structured troubleshooting workflows for CloudWatch alarms, metric gaps, alert fatigue, and SLI/SLO definitions so engineers can resolve observability issues systematically instead of guessing. ## Core Features & Use Cases - Alarm Investigation Decision Trees: Step-by-step flows for ALARM, INSUFFICIENT_DATA, and flapping alarm states, including evaluation periods, datapoints-to-alarm, and missing-data treatment. - Per-Service Metric & Threshold Reference: Recommended warning/critical thresholds for EC2, RDS, Lambda, ALB, ECS, DynamoDB, ElastiCache, API Gateway, SQS, and SNS with ready-to-run AWS CLI commands. - CloudWatch Best Practices: Metric math expressions (error rate, cache hit ratio), composite alarms, cross-account dashboards, CloudWatch Agent configuration, and EMF for Lambda. - Use Case: An on-call engineer sees a flapping CPU alarm. The Skill guides them to widen evaluation periods, switch to an anomaly detection band, and build a composite alarm combining CPU and error rate to cut noise. ## Quick Start Ask the agent to investigate why a specific CloudWatch alarm is stuck in INSUFFICIENT_DATA and recommend the right threshold and evaluation period settings.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I troubleshoot a CloudWatch alarm stuck in INSUFFICIENT_DATA?▼

INSUFFICIENT_DATA usually means the metric is not being published. Verify the metric exists with list-metrics, check that dimensions match exactly (case-sensitive), confirm the CloudWatch agent is running, and ensure the alarm period is not shorter than the metric publishing frequency.

How do I reduce CloudWatch alarm noise and alert fatigue?▼

Classify alarms into critical, warning, and info tiers, then increase evaluation periods for non-critical alarms, use composite alarms to combine related signals, and apply anomaly detection bands for variable workloads instead of static thresholds.

What CloudWatch metrics should I monitor for RDS?▼

Key RDS metrics include CPUUtilization, FreeableMemory, DatabaseConnections, ReadIOPS/WriteIOPS, FreeStorageSpace, ReplicaLag, SwapUsage, and DiskQueueDepth. The Skill provides warning and critical thresholds for each, such as FreeableMemory below 512MB as a warning.

How do I create a CloudWatch alarm on error rate using metric math?▼

Use put-metric-alarm with a metrics array containing two source metrics (errors and total requests) plus a math expression like (errors/total)*100. Set ReturnData to true only on the expression, then alarm on the computed percentage threshold.

When should I use anomaly detection instead of static thresholds?▼

Use anomaly detection for metrics with natural variation or seasonality, such as request counts and latency, where a fixed threshold causes false positives. Static thresholds remain appropriate for hard limits like disk space or status check failures.