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/thefear078/cursor-kit-for-ai --skill monitoring-check-thefear078
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring-check
Source: https://github.com/thefear078/cursor-kit-for-ai/tree/main/plugins/devops/skills/monitoring-check
Command: npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill monitoring-check-thefear078

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often cannot answer "is the service broken for users right now" because metrics are missing, alerts are noisy or misconfigured, and dashboards bury the signal. This Skill audits the full observability stack so gaps are found before an outage does. ## Core Features & Use Cases - Four-layer audit: Reviews metrics coverage (RED/USE methods), alert quality, dashboard design, and log hygiene in a fixed order. - Alert quality tests: Validates every alert against actionable, urgent, and user-impacting criteria, with PromQL examples for ratio-based alerting and absence detection. - Verification commands: Ships runnable curl/jq checks against the Prometheus API to confirm targets are scraped and metrics actually arrive. - Use Case: After deploying a new service, run this review to discover the app exposes /metrics but no scrape job exists, histogram buckets are defaults, and no alert fires when the exporter dies. ## Quick Start Ask the AI to review the monitoring setup for your service using the monitoring-check skill and report critical observability gaps.

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 coverage for a service?▼

Check metrics coverage using the RED method (rate, errors, duration) per service and USE method (utilization, saturation, errors) per resource. Verify the pipeline end-to-end by querying the Prometheus targets API and confirming metrics arrive with data.

What makes a good Prometheus alert rule?▼

A good alert is actionable, urgent, and user-impacting. Alert on symptoms like error ratio or SLO burn using rate ratios with a for-duration, not instant absolute values or causes like high CPU.

How do I reduce noisy alerts in Prometheus?▼

Run a noise audit: any alert that fired more than three times last month without action taken should have its threshold fixed or be deleted. Split severities into page and warn channels so real pages are not ignored.

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

A dead exporter makes everything look healthy because no data arrives. Use the absent() function in Prometheus to alert on missing metrics, and always alert on up == 0 for dead targets.

What should a structured logging setup include?▼

Use JSON logs with level, timestamp, and request_id fields, propagating request_id across services. Reserve ERROR for items needing action, keep secrets and PII out of logs, and configure retention and rotation.