Skip to content

mattgierhart/PRD-driven-context-engineering / .claude/skills/prd-v08-monitoring-setup

prd-v08-monitoring-setup

Verified

Define monitoring strategy, metrics collection, and alerting thresholds during PRD v0.8 Deployment & Ops. Triggers on requests to set up monitoring, define alerts, or when user asks "what should we monitor?", "alerting strategy", "observability", "metrics", "SLOs", "dashboards", "monitoring setup". Outputs MON- entries with monitoring rules and alert configurations.

FileKindSize
SKILL.mdskill md14.7 KB
assets/mon-template.mdmarkdown4.8 KB
references/dashboard-guide.mdmarkdown20.4 KB
references/monitoring-stack.mdmarkdown9.6 KB
references/slo-guide.mdmarkdown12.4 KB

assets/mon-template.md

View on GitHub
# MON-XXX: [Monitoring Rule Title]

**ID**: MON-XXX
**Type**: [Metric | Alert | Dashboard | SLO]
**Layer**: [Infrastructure | Application | Business | User Experience]
**Owner**: [Team responsible for this metric/alert]
**Created**: YYYY-MM-DD
**Last Updated**: YYYY-MM-DD

---

## For Metric Type

**Name**: `[metric.name.format]`
**Description**: [What this measures and why it matters]
**Unit**: [count | ms | percentage | bytes | requests/sec]
**Source**: [Where this comes from - APM tool, logs, custom instrumentation]
**Aggregation**: [avg | sum | min | max | p50 | p95 | p99]
**Retention**: [How long to keep data - e.g., 90 days, 1 year]
**Collection Frequency**: [How often to collect - e.g., 10s, 1m, 5m]

**Baseline**: [Expected normal range under typical load]
**Context**: [Additional context that helps interpret this metric]

---

## For Alert Type

**Metric**: [MON-YYY reference or metric name]
**Condition**: [Threshold expression - e.g., > 500ms, < 95%, >= 10]
**Window**: [Time window for evaluation - e.g., 5 minutes, 15 minutes]
**Severity**: [Critical | Warning | Info]
**Runbook**: [RUN-XXX to follow when this alert fires]

**Notification**:
- **Channel**: [Slack (#channel), PagerDuty, Email, SMS]
- **Recipients**: [Team, role, or individuals - e.g., "Backend on-call", "Tech Lead"]
- **Escalation**: [If not acknowledged within X minutes, escalate to Y]

**Silencing**:
- **Conditions**: [When to suppress - e.g., during maintenance windows]
- **Windows**: [DEP-XXX references for planned maintenance]
- **Override**: [Who can manually silence and for how long]

**False Positive Handling**: [Known scenarios that trigger but aren't incidents]

---

## For Dashboard Type

**Purpose**: [What questions this dashboard answers]
**Audience**: [Who uses this dashboard - e.g., on-call engineers, leadership, ops team]
**URL**: [Link to dashboard in monitoring tool]

**Panels**:
1. [Panel name] - [What it shows and why]
2. [Panel name] - [What it shows and why]
3. [Panel name] - [What it shows and why]

**Refresh**: [How often to update - e.g., 30 seconds, 1 minute, 5 minutes]
**Time Range**: [Default time window - e.g., last 1 hour, last 24 hours]

**Usage Notes**: [How to interpret the dashboard, what to look for]

---

## For SLO Type

**Objective**: [What we promise - clear, measurable statement]
**Target**: [Percentage - e.g., 99.9%, 99.95%]
**Window**: [Evaluation period - e.g., Rolling 30 days, Calendar month]
**Error Budget**: [Calculated allowed downtime - e.g., 43.2 minutes/month for 99.9%]

**Measurement**:
- **Success Criteria**: [What counts as "good" - e.g., non-5xx responses, latency < 500ms]
- **Failure Criteria**: [What counts as "bad" - e.g., 5xx responses, latency >= 500ms]
- **Data Source**: [Where measurements come from]

**Alerting**:
- **50% budget consumed**: [Warning level action]
- **75% budget consumed**: [Critical level action]
- **90% budget consumed**: [Emergency level action]
- **100% budget consumed**: [Breach protocol]

**Burn Rate Alerts**:
- **Fast burn** (1 hour window): Alert if consuming budget at 14.4x rate
- **Slow burn** (6 hour window): Alert if consuming budget at 6x rate

---

## Linked IDs

**Related Specifications**:
- [API-XXX]: [How this relates to API contracts]
- [UJ-XXX]: [How this relates to user journeys]
- [KPI-XXX]: [How this relates to business metrics]
- [BR-XXX]: [How this enforces business rules]

**Related Operations**:
- [RUN-XXX]: [Runbooks triggered by this monitoring]
- [DEP-XXX]: [Deployment procedures that affect this]
- [MON-YYY]: [Related monitoring entries]

**Test Coverage**:
- [TEST-XXX]: [Tests that validate this monitoring works]

---

## Implementation

**Configuration**:
```yaml
# Example configuration for monitoring tool
# (Adjust syntax for your specific tool: Datadog, New Relic, Prometheus, etc.)

[Paste configuration here]
```

**Code Location**:
- **Instrumentation**: [File path where metric is emitted]
- **Alert Definition**: [File path or UI location where alert is configured]
- **Dashboard**: [File path or URL where dashboard is defined]

---

## Validation

**Before Deployment**:
- [ ] Metric collects successfully in staging
- [ ] Alert fires when condition is met (test in staging)
- [ ] Dashboard renders correctly
- [ ] Runbook linked and accessible
- [ ] Notification channels tested
- [ ] Baseline established from staging data

**After Deployment**:
- [ ] Metric appears in production monitoring
- [ ] Alert threshold tuned based on production traffic
- [ ] No false positives in first 7 days
- [ ] Team trained on runbook procedures

---

## Version History

| Version | Date | Change | Updated By |
|---------|------|--------|------------|
| 1.0 | YYYY-MM-DD | Initial creation | [Name] |
| | | | |

---

## Notes

[Any additional context, lessons learned, or edge cases worth documenting]

---

*Template: Use this to create MON-XXX entries in `SoT.DEPLOYMENT.md`*
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall