production-monitoring-setup

Generate hypercare monitoring documentation with dashboards, alert thresholds, and escalation procedures.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill production-monitoring-setup-vanduc2514
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: production-monitoring-setup
Source: https://github.com/vanduc2514/hackathon-lablab-ibm-bob/tree/main/.bob/skills/production-monitoring-setup
Command: npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill production-monitoring-setup-vanduc2514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a migration, teams need intensive post-deployment monitoring but often lack a concrete plan for what to watch, which thresholds to set, and how to escalate issues during the critical hypercare period. ## Core Features & Use Cases - Metrics Dashboards: Defines critical application, infrastructure, database, dependency, and business metrics with target, warning, and critical thresholds. - Alert Configuration: Produces severity-tiered alert rules (P0-P3) with notification channels and runbook links for tools like Datadog, Prometheus, and CloudWatch. - Escalation & Scheduling: Specifies monitoring review cadences, on-call responsibilities, and multi-level escalation procedures with response timeframes. - Use Case: After migrating a Spring Boot e-commerce platform, generate a hypercare_monitoring_setup.md defining P95 latency alerts, database connection pool thresholds, and a 24/7 week-one monitoring schedule. ## Quick Start Create the hypercare monitoring setup document for my migrated application using the optimization report and target architecture design.

Frequently Asked Questions about production-monitoring-setup

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

FAQPage Schema
How do I set up monitoring after a production migration?▼

Define critical metrics with thresholds across application, infrastructure, database, and dependency layers, then configure severity-tiered alerts and escalation procedures. This skill generates a hypercare_monitoring_setup.md covering dashboards, alert rules, and review schedules.

What metrics should I monitor during hypercare?▼

Track application performance (throughput, P95/P99 latency, error rates), infrastructure (CPU, memory, disk), database (query time, connection pool, replication lag), external dependencies, and business metrics like transaction success rates.

Which monitoring tools does this support?▼

The documentation covers Datadog dashboard and alert rule syntax, Prometheus PromQL queries, and CloudWatch alarm definitions. Configurations include concrete examples like error rate alerts and latency thresholds.

How should alert severity levels be defined?▼

Use four tiers: P0 for outages requiring 15-minute response and paging, P1 for significant degradation within 30 minutes, P2 for minor issues within 2 hours, and P3 for warning trends reviewed next business day.

What inputs are needed to create monitoring documentation?▼

You need the optimization report for performance baselines, the target architecture design for system components, the testing strategy for SLAs, plus team on-call structure and available monitoring platforms.