monitoring-setup-guide
Write a monitoring setup guide for a service — defining what to measure, how to alert on it, and how to build the observability stack covering the four golden signals, business metrics, log strategy, distributed tracing, alerting rules, dashboard layout, and observability debt. Use when asked to set up monitoring for a service, define alerting strategy, write an observability plan, create a dashboard specification, or document logging standards for a team. Produces a metric definitions table, alert rules specification, dashboard layout wireframe, log schema, tracing setup checklist, and monito
npx skills add mohitagw15856/pm-claude-skills --skill monitoring-setup-guide --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Monitoring Setup Guide Skill Produce a complete monitoring setup guide for a service — defining exactly what to measure, how to structure logs, how to configure alerts with actionable thresholds, and how to build dashboards that answer real operational questions. A good monitoring guide eliminates "we don't know what's happening in production" as a root cause category, and gives on-call engineers a single source of truth for what healthy looks like. ## Required Inputs Ask for these if not already provided: - **Service name and description** — what the service does and its role in the system - **Tech stack** — language, framework, and infrastructure (e.g. Go/gRPC on Kubernetes, Python/FastAPI on ECS) - **Current monitoring tooling** — Datadog, Prometheus + Grafana, CloudWatch, New Relic, Honeycomb, or none yet - **Key user journeys** — the 2–4 most important things a user or consumer does with the service (these drive what to alert on) - **Existing alerts** — paste any existing alert configurations or describe what's currently monitored ## Output Format --- # Monitoring Setup Guide: [Service Name] **Team:** [Team name] | **Tech lead:** [Name] **Stack:** [Language/Framework] on [In
- Required Inputs
- Output Format
- 1. Monitoring Philosophy
- 2. The Four Golden Signals
- Latency
- Traffic
- Errors
- Saturation
- 3. Business Metrics
- 4. Log Strategy
- Structured Logging Schema
- Log Levels — When to Use Each
- What NOT to Log
- 5. Distributed Tracing Setup
What does the monitoring-setup-guide skill do?
Write a monitoring setup guide for a service — defining what to measure, how to alert on it, and how to build the observability stack covering the four golden signals, business metrics, log strategy, distributed tracing, alerting rules, dashboard layout, and observability debt. Use when asked to set up monitoring for a service, define alerting strategy, write an observability plan, create a dashboard specification, or document logging standards for a team. Produces a metric definitions table, alert rules specification, dashboard layout wireframe, log schema, tracing setup checklist, and monito
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill monitoring-setup-guide --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.