metrics-monitoring_skill

This skill helps you instrument applications with RED and USE metrics, build dashboards, and configure alerts for proactive monitoring.
  • Python

3

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dasien/claudemultiagenttemplate --skill metrics-monitoring

  • SKILL.md10.6 KB

Overview

This skill implements application metrics (RED, USE, Four Golden Signals), builds monitoring dashboards, and configures alerting strategies so teams detect and resolve issues before users are impacted. It provides instrumentation patterns, collection choices (Prometheus, StatsD, CloudWatch, DataDog), alert rules, and dashboard templates for production services. The output is practical code snippets, alert rules, and best-practice guidance for reliable observability.

How this skill works

The skill instruments services with counters, gauges, histograms, and summaries to capture rate, errors, duration, utilization, and saturation. It wires those metrics into a collection backend (e.g., Prometheus) and deploys dashboards and alert rules (Grafana + Prometheus alerts or equivalent). It also includes patterns like automatic decorators, background resource polling, and example alert expressions for error rate, latency, and resource saturation.

When to use it

  • Deploying services to production
  • Detecting incidents and enabling fast response
  • Tracking SLAs/SLOs and business KPIs
  • Capacity planning and performance tuning
  • Establishing on-call alerting and runbooks

Best practices

  • Use RED for request-driven services and USE for resources
  • Record percentiles (p95/p99) for latency rather than averages
  • Limit label cardinality; avoid user IDs and timestamps
  • Alert on symptoms (error rate, latency, saturation), not on root causes
  • Define SLOs and alert on SLO burn or violations
  • Create runbooks and test alerts regularly to avoid alert fatigue

Example use cases

  • Instrument a Flask API with Prometheus metrics and expose /metrics for scraping
  • Create Grafana dashboards: request rate, error rate, p95 latency, and connection pool gauges
  • Define Prometheus alert rules: high error rate, P95 latency breach, CPU > 80%, DB pool near limit
  • Use a decorator to auto-instrument important functions (calls, errors, duration)
  • Track business metrics (orders, revenue) alongside technical metrics to correlate customer impact

FAQ

Choose based on environment and team expertise: Prometheus + OpenMetrics works well for on-prem/kubernetes; CloudWatch integrates tightly with AWS; DataDog offers a managed full-stack option. The instrumentation approach (counters/gauges/histograms) is the same across backends.

How do I avoid alert fatigue?

Alert on symptoms and SLOs, set reasonable thresholds and ‘for’ durations, limit noisy alerts, group related alerts, and maintain runbooks so each alert is actionable.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational