monitoring-check

Audit Prometheus metrics, alert rules, Grafana dashboards, and logs for observability gaps.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill monitoring-check-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring-check
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/devops/skills/monitoring-check
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill monitoring-check-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often cannot answer "is the service broken for users right now" because metrics are incomplete, alerts are noisy or missing, and dashboards bury the signal. This Skill audits the full observability stack so gaps are found before an outage does. ## Core Features & Use Cases - Metrics Coverage Audit: Verifies RED (rate, errors, duration) and USE (utilization, saturation, errors) metrics exist per service, and checks the Prometheus scrape pipeline end-to-end with curl commands against /targets, /metrics, and query APIs. - Alert Quality Review: Applies the actionable/urgent/user-impacting test to every alert, enforces ratio-based expressions with for: durations, severity split between page and warn, and absence-of-data detection via absent(). - Dashboard and Log Inspection: Checks dashboard layout (RED overview, saturation, dependencies, deploy annotations) and log hygiene (structured JSON, request_id propagation, no secrets, retention configured). - Use Case: After deploying a new service, run this review to confirm Prometheus is actually scraping it, error-ratio alerts exist with runbook links, and the on-call dashboard answers health questions in under 30 seconds. ## Quick Start Ask the agent to review the monitoring setup for your service and report critical observability gaps, noisy alerts, and recommended additions.

Frequently Asked Questions about monitoring-check

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

FAQPage Schema
How do I audit Prometheus monitoring for a new service?▼

Verify the scrape pipeline end-to-end: check active targets via the Prometheus /api/v1/targets endpoint, confirm the app exposes /metrics, and query the metric to confirm data arrives. Then validate RED metrics (rate, errors, duration) exist per endpoint.

What makes a good Prometheus alert rule?▼

A good alert is actionable, urgent, and user-impacting. Alert on symptoms like error ratio or latency SLO burn using rate ratios with a `for:` duration, not instant absolute thresholds or causes like high CPU. Include severity labels and a runbook link.

How do I reduce noisy alerts in Prometheus?▼

Audit any alert that fired more than three times last month without action taken and fix its threshold or delete it. Split severity into page versus warn channels, since mixing both in one channel guarantees ignored pages.

Why does my monitoring look healthy when the service is down?▼

A dead exporter makes everything look healthy because no data arrives. Add absence-of-data alerts using the `absent()` function and alert on `up == 0` so missing metrics themselves trigger a page.

What metrics should every service expose?▼

Per the RED method: request rate by endpoint and status, 5xx errors as a ratio of traffic, and latency histograms for p50/p95/p99. Add USE metrics per resource (CPU, memory, disk, connection pools) plus at least one business metric like orders per minute.