monitoring

Name: monitoring
Availability: InStock
Author: Paulund

Set up logging, metrics, tracing, and alerting for applications and infrastructure.

Updated Aug 23, 2026

Search Tags:#monitoring #logging #metrics #observability #tracing #alerting

Ready to run

npx skills add https://github.com/paulund/ai --skill monitoring-paulund

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/paulund/ai/tree/main/monitoring/skills/monitoring
Command: npx skills add https://github.com/paulund/ai --skill monitoring-paulund

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you set up and manage comprehensive monitoring solutions for your applications and infrastructure, ensuring optimal performance and reliability.

Core Features & Use Cases

Observability: Implement logging, metrics, and tracing for deep system insights.
Alerting: Configure proactive alerts for critical issues to minimize downtime.
Use Case: When deploying a new microservice, use this Skill to define structured logging, essential performance metrics (latency, error rate), and set up alerts for high error rates or service unavailability.

Quick Start

Configure structured logging and essential performance metrics for your application.

Frequently Asked Questions about monitoring

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

FAQPage Schema

How do I set up application monitoring for a new microservice?▼

Application monitoring for a new microservice requires configuring structured logging, collecting essential performance metrics like latency and error rate, and defining alert rules for high error rates or service unavailability to ensure reliability.

What is observability and how does tracing improve incident response?▼

Observability provides deep system insights by combining logging, metrics, and tracing. Tracing improves incident response by tracking requests across services, enabling performance analysis and faster identification of bottlenecks during critical issues.

How do I configure alerting rules for high error rates and downtime?▼

Configuring alerting for high error rates and downtime involves defining proactive alert rules based on aggregated metrics. This structured notification system minimizes downtime by alerting you to critical issues before they impact service availability.

What's the best way to collect metrics and structured logs for infrastructure observability?▼

The best way to achieve infrastructure observability is by implementing structured logging alongside metric aggregation. This approach collects performance data systematically, enabling deep system insights and supporting proactive incident response.

Can I use this monitoring setup for both applications and infrastructure?▼

Yes, this monitoring setup facilitates solutions for both applications and infrastructure. It addresses observability requirements across your entire stack by utilizing structured data collection for logging, metrics, and tracing.

Why do I need structured logging instead of basic logging for performance analysis?▼

Structured logging is needed for performance analysis because it formats data systematically for aggregation and querying. Unlike basic logging, it enables proactive notification systems and deep observability across microservices.