Monitoring Setup

Define monitoring plans with SLIs, dashboards, and alerts for production services.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MS33834/AI-SKILL --skill monitoring-setup-ms33834
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Monitoring Setup
Source: https://github.com/MS33834/AI-SKILL/tree/main/skills/monitoring-setup
Command: npx skills add https://github.com/MS33834/AI-SKILL --skill monitoring-setup-ms33834

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from service observability by turning a vague production system into a clear monitoring plan with actionable signals, dashboards, and alerts.

Core Features & Use Cases

  • SLI Definition: Identifies the most important service indicators such as latency, error rate, throughput, and saturation.
  • Dashboard Planning: Outlines the key panels needed to understand health, load, and failure patterns at a glance.
  • Alert Design: Separates symptom-based alerts from cause-based alerts and ties them to thresholds and escalation paths.
  • Use Case: A team launching a payment webhook processor can use this Skill to define p99 latency goals, page-worthy failures, and dashboards for queue depth and delivery reliability.

Quick Start

Describe your service and any SLOs, and I will produce a monitoring plan with SLIs, dashboards, alerts, log-based metrics, and on-call guidance.

Frequently Asked Questions about Monitoring Setup

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

FAQPage Schema
How do I set up monitoring dashboards and alerts for a new service?▼

To set up monitoring dashboards and alerts, define your service's SLIs and SLOs first. This produces a complete monitoring plan with symptom-based alerts, log-based metrics, and on-call escalation guidance.

What is the best way to reduce alert fatigue for production systems?▼

Reducing alert fatigue requires separating symptom-based alerts from cause-based alerts. This approach ties actionable thresholds to escalation paths, ensuring on-call teams only receive page-worthy failures.

How do I define SLIs and SLOs for a service lacking clear metrics?▼

Defining SLIs and SLOs involves identifying critical service indicators like latency, error rate, throughput, and saturation. This establishes baseline reliability targets for your dashboards and alerts.

What metrics should a service dashboard include for observability?▼

A service dashboard for observability should include key panels for health, load, and failure patterns. This provides an at-a-glance view of p99 latency, queue depth, and delivery reliability.

When do I need log-based metrics for on-call reviews?▼

You need log-based metrics for on-call reviews when expanding observability beyond standard indicators. They help track specific failure patterns and delivery reliability within your dashboards.

Can I use this monitoring plan for a payment webhook processor?▼

Yes, you can use this monitoring plan for a payment webhook processor. It will generate p99 latency goals, page-worthy failure alerts, and dashboards for queue depth and delivery reliability.