What problem does it solve?
This Skill helps you create a complete monitoring design that covers what to monitor, how often to check, which thresholds trigger alerts, and how to notify and escalate so incidents are detected early and handled consistently.
Core Features & Use Cases
- MECE-based monitoring structure: Breaks monitoring design into clear sections (dead/alive, resources, application, network, security, logs, notifications, dashboards, operations).
- Tool-agnostic design with concrete examples: Supports major monitoring platforms like CloudWatch, Datadog, and Mackerel by specifying the monitoring items and expected behaviors.
- Alerting and operations readiness: Defines notification channels (SNS/PagerDuty/Slack/email), priority levels (P1–P3), and escalation flows including time-based rules and on-call assumptions.
Example use case: you need to produce the “Monitoring” non-functional design document for a new AWS-based system and want a standardized baseline that can be reviewed and kept consistent across projects.
Quick Start
Use this skill to generate the monitoring design document “基盤概要設計_監視編.md” with dead/alive, resource, application, network, security, log, notification, and dashboard sections for your system.
