monitor

Implements structured logging, metrics, alerting, and health checks for production services.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill monitor-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitor
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/personas/devops/monitor
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill monitor-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires prometheus_client.

What problem does it solve? Production services often lack consistent observability, leaving teams blind to failures until users report them. This Skill provides concrete patterns for structured logging, metrics instrumentation, alerting rules, and health checks so systems surface problems proactively. ## Core Features & Use Cases - Structured JSON Logging: Python logging configuration with JSON formatting, correlation IDs, and exception capture for searchable log aggregation. - Metrics Instrumentation: Prometheus-style counters, histograms, and gauges covering the four golden signals (latency, traffic, errors, saturation). - Health Checks & Alerting: Aggregated health check endpoints with healthy/degraded/unhealthy states, plus Prometheus alert rules that fire on symptoms rather than causes. - Use Case: When adding observability to a new microservice, invoke this Skill to generate the logging setup, metrics endpoint, health check aggregation, and alert rules in one pass. ## Quick Start Ask Claude to add structured logging, Prometheus metrics, and a health check endpoint to your service using the monitor skill.

Frequently Asked Questions about monitor

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

FAQPage Schema
How do I set up structured JSON logging in Python?▼

Create a custom logging.Formatter that serializes each record to JSON with timestamp, level, message, and module fields, then attach it to a StreamHandler. Add contextual fields like request_id via the extra parameter on log calls.

How to add Prometheus metrics to a Python service?▼

Use the prometheus_client library to define Counter, Histogram, and Gauge metrics, instrument handlers with decorators or explicit calls, and expose them via start_http_server on a /metrics endpoint for Prometheus to scrape.

What metrics should every service dashboard show?▼

Dashboards should display the four golden signals: request rate, error rate, latency percentiles (p50, p95, p99), and saturation (CPU, memory, disk, connections). Overlay recent deployments and current health check status for context.

Should I alert on every metric threshold?▼

No. Alert only on actionable symptoms like elevated error rates or high P99 latency, not on every metric or cause. Alerting on everything creates alert fatigue, causing teams to ignore real incidents.

When should I not use this monitoring skill?▼

Do not use it for CPU or memory profiling of application bottlenecks, which belongs to performance profiling workflows, or for diagnosing Linux networking and connectivity issues, which require network diagnostic tools rather than application-level observability.