monitor

Instrument JSON logs, metrics, health checks, and alerting for production services.

4|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/AreteDriver/ai_skills --skill monitor-aretedriver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor
Source: https://github.com/AreteDriver/ai_skills/tree/main/skills/monitor
Command: npx skills add https://github.com/AreteDriver/ai_skills --skill monitor-aretedriver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams implement robust observability by defining consistent logging, metrics, alerting, and health-check patterns for production services, enabling proactive incident detection and faster remediation.

Core Features & Use Cases

  • Structured logging using JSON with traceability via correlation IDs across service boundaries.
  • Instrumentation of the four golden signals: latency, traffic, errors, saturation.
  • Health checks for services and health status aggregation for dashboards and incident response.
  • Alerting rules that trigger on symptoms (not causes) to reduce alert fatigue.
  • Guidelines for dashboards, incident response workflows, and how to evolve observability over time.

Quick Start

Deploy a minimal observability setup in a new service: enable JSON logs, add a basic health-check endpoint, and configure simple latency and error-rate metrics to surface in a dashboard.

Frequently Asked Questions about monitor

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

FAQPage Schema
How do I set up observability with structured logging and metrics for a new microservice?

Observability for a new microservice is established by enabling structured JSON logs with correlation IDs, instrumenting the four golden signals, and adding a basic health-check endpoint to surface uptime and incident data on dashboards.

What are the four golden signals of SRE monitoring and how do I instrument them?

The four golden signals of SRE monitoring are latency, traffic, errors, and saturation. You instrument them by configuring metrics collection for each signal to standardize health visibility and alerting across production services.

How do I configure alerting rules to reduce alert fatigue in production systems?

Alerting rules reduce alert fatigue when they trigger on symptoms rather than underlying causes. By configuring alerts based on aggregated health status and golden signal thresholds, teams avoid noisy false positives during incident response.

Why do I need correlation IDs in JSON logs across microservices?

Correlation IDs in JSON logs are required to trace requests across microservice boundaries. Structured logging with these traceability identifiers standardizes log formats and accelerates root cause analysis during incident remediation.

Can I use this monitoring approach for both monoliths and microservices?

Yes, this monitoring approach applies to both monoliths and microservices. It standardizes observability by enforcing structured logging, golden signal metrics, and documented health checks regardless of your production architecture.

What's the best way to aggregate health checks for service dashboards?

Aggregating health checks for dashboards is best achieved by implementing standardized health-check endpoints across services. This provides a unified health status view for incident response workflows and proactive uptime monitoring.