
Setup Monitoring
- 1 installs
- 27 repo stars
- Updated April 25, 2026
- girijashankarj/cursor-handbook
Lightweight guide to scope monitoring, define 3-5 key metrics, set alert thresholds and severities, and list dashboard panels for a service.
About
Guides setting up or extending monitoring with metrics, logs, and alerts for a service. A developer uses it to set up monitoring or add alerts.
- Defines 3-5 key metrics with structured logging
- Proposes alert thresholds and severity levels
Setup Monitoring by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,173 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Data as of Jul 22, 2026 (Skillselion catalog sync)
npx skills add https://github.com/girijashankarj/cursor-handbook --skill setup-monitoringAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 27 |
| Last updated | April 25, 2026 |
| Repository | girijashankarj/cursor-handbook ↗ |
What it does
Lightweight guide to scope monitoring, define 3-5 key metrics, set alert thresholds and severities, and list dashboard panels for a service.
Files
Skill: Setup monitoring
Trigger
When the user asks to set up monitoring, add alerts, or configure dashboards.
Steps
1. Scope — Identify what to monitor (API latency, errors, DB, queue depth) and where (cloud provider, vendor). 2. Metrics — Define 3–5 key metrics (e.g. request rate, error rate, p99 latency); use structured logging with correlationId. 3. Alerts — Propose thresholds (e.g. error rate > 1%, p99 > 2s) and severity; document in runbook. 4. Dashboard — List panels to add (time series, status); use placeholders for dashboard URLs. 5. Logs — Remind: no PII or secrets; JSON format; include correlationId per project rules.
Rules
- Follow
.cursor/rules/devops/monitoring.mdc. Use placeholder resource names.