skills.rest
kazdenc
kazdencCOMMUNITY
Explore all skills by this author →
𝕏@kazdencGitHub

monitor

Set up production monitoring with error tracking, SLOs, and alerting.

42|5|Updated Mar 8, 2026
Search Tags:#monitoring#production#observability#reliability#alerting#SLOs
One-click install
npx skills add https://github.com/kazdenc/builder-skills --skill monitor-kazdenc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitor
Source: https://github.com/kazdenc/builder-skills/tree/main/.claude/skills/dev/deploy/monitor
Command: npx skills add https://github.com/kazdenc/builder-skills --skill monitor-kazdenc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you establish comprehensive monitoring for production applications, ensuring reliability and quick issue detection through error tracking, alerts, dashboards, and SLOs.

Core Features & Use Cases

  • Four Pillars of Monitoring: Covers errors, performance, availability, and business metrics.
  • Actionable Alerting: Configures alerts based on critical signals with clear response expectations.
  • SLO Definition: Sets Service Level Objectives for key services and manages error budgets.
  • Use Case: When deploying a new microservice, use this Skill to set up its health check endpoint, configure Sentry for error tracking, define PagerDuty alerts for critical failures, and establish an SLO for API availability.

Quick Start

Use the monitor skill to set up monitoring for the new user authentication service.

Frequently Asked Questions about monitor

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

FAQPage Schema
How do I set up comprehensive production monitoring for a new microservice?▼

Production monitoring setup requires configuring error tracking, performance metrics, availability checks, and business KPIs. You establish a health check endpoint, integrate error tracking, and define alerts to ensure quick issue detection for the new service.

What are Service Level Objectives and how do error budgets work?▼

Service Level Objectives (SLOs) define target reliability levels for key services. Error budgets represent the allowable threshold of unreliability against those SLOs, helping you balance feature velocity with operational stability.

Does this monitoring setup integrate with Sentry and PagerDuty?▼

Yes, the monitoring setup requires integration with services like Sentry for error tracking, PagerDuty for critical failure alerts, and Real User Monitoring (RUM) tools to capture frontend performance data.

What is the best way to configure actionable alerting for production applications?▼

Actionable alerting is configured based on critical signals with clear response expectations. It targets errors, performance drops, and availability failures rather than noise, ensuring operators know exactly when and how to respond.

Can I track business KPIs alongside availability checks in my dashboards?▼

Yes, dashboards are outlined to include essential components for incident response and operational visibility. They combine availability checks, business KPIs, performance metrics, and error tracking into a unified operational view.

Related Skills

Explore More Software Engineering Skills→
burgebjburgebj

setup-deploy

Configure deployment settings and write them to a configuration file.

Community
Advanced
leonardoteodorooleonardoteodoroo

slo-implementation

Define SLIs, SLOs, and error budgets for services using Prometheus metrics.

Community
Advanced
tuanfungtuanfung

observability-and-instrumentation

Set up OpenTelemetry, Prometheus, and logging for application monitoring.

Community
Advanced
JeffallanJeffallan
10.9k

sre-engineer

Define SLOs, SLIs, and error budgets for production reliability.

Community
Advanced