Forge-Production-Monitoring

Define monitoring signals, thresholds, baselines, and capacity forecasts for production systems.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-production-monitoring-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Production-Monitoring
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/09-Operations/Forge-Production-Monitoring
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-production-monitoring-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production systems fail silently when teams lack a defined monitoring strategy: alerts fire without actionability, baselines are guessed rather than observed, and capacity issues surface only after they become incidents. This Skill structures how teams decide what to observe, what healthy looks like, and which signals deserve alerts. ## Core Features & Use Cases - Monitoring Strategy Definition: Establishes observation coverage across health, performance, and capacity dimensions for every critical user path. - Signal and Threshold Design: Grounds thresholds in observed baselines with recorded rationale instead of guesses. - Capacity Forecasting: Projects trends from observed data to feed procurement and scaling decisions before capacity becomes an incident. - Alert-Worthiness Judgement: Ensures every alert is actionable and routes everything else to dashboards, reducing alert fatigue. - Use Case: When onboarding a new service, use this Skill to define its signal catalogue, set baseline-derived thresholds, and produce a capacity forecast that infrastructure teams can act on. ## Quick Start Ask the AI to define a monitoring strategy with signals, thresholds, and a capacity forecast for your service using its architecture and incident history.

Frequently Asked Questions about Forge-Production-Monitoring

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

FAQPage Schema
How do I define a monitoring strategy for a production system?▼

Start by mapping critical user paths, then define signals across health, performance, and capacity dimensions for each path. Ground thresholds in observed baselines rather than guesses, and record the rationale for every threshold you set.

How to reduce alert fatigue and improve alert quality?▼

Apply alert-worthiness judgement: every alert must be actionable, and everything else belongs on a dashboard. Review alert noise regularly against incident history and measure alert fatigue as a signal quality problem to be treated.

Does this Skill respond to firing alerts or incidents?▼

No, alert response belongs to incident management. This Skill defines the signals and thresholds that generate alerts; responding to a firing alert, investigating logs, or executing capacity changes are handled by separate operational skills.

How do I forecast capacity from monitoring trends?▼

Maintain performance baselines from observed data, then extrapolate trends to project future resource needs. Feed these forecasts into procurement or scaling decisions before capacity shortfalls become production incidents.

When should I not use a monitoring strategy skill?▼

Do not use it for responding to active alerts, investigating log evidence, or executing infrastructure changes. It also does not select monitoring tools, since tooling choices belong to project documentation.