monitoring-expert

Configure logs, metrics, and traces for services with Prometheus, Grafana, and OpenTelemetry.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/lamb92009/claude-skills --skill monitoring-expert-lamb92009
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-expert
Source: https://github.com/lamb92009/claude-skills/tree/main/monitoring-expert
Command: npx skills add https://github.com/lamb92009/claude-skills --skill monitoring-expert-lamb92009

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Establishes comprehensive observability by wiring logs, metrics, traces, and alerting across services to improve reliability, performance, and incident response.

Core Features & Use Cases

  • Instrument applications with structured logging, metrics, and traces; configure dashboards in Prometheus or Grafana; implement alerting rules; perform load testing and profiling for capacity planning.
  • Use cases include real-time incident detection for microservices and serverless workloads, capacity forecasting, and performance optimization across hybrid environments.

Quick Start

Configure your services to emit logs, metrics, and traces and connect them to Prometheus/Grafana for centralized dashboards.

Frequently Asked Questions about monitoring-expert

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

FAQPage Schema
How do I set up end-to-end observability with logs, metrics, and traces for microservices?

End-to-end observability is established by instrumenting services to emit structured logs, appropriate metric types, and traces, then routing them to Prometheus and Grafana for centralized dashboards and alerting. This enables quick incident detection and performance tuning across microservices.

Can I configure Prometheus alerting rules and Grafana dashboards for containerized apps?

Yes, Prometheus alerting rules and Grafana dashboards can be configured for containerized apps. The setup involves instrumenting applications to emit metrics and connecting them to Prometheus for data collection and Grafana for visualizing real-time incident detection.

What's the best way to implement structured logging and health checks for serverless functions?

The best way to implement structured logging and health checks for serverless functions is by instrumenting them with OpenTelemetry to emit traces and logs. This satisfies observability requirements and enables capacity forecasting and performance optimization.

Does OpenTelemetry work with legacy monoliths for tracing and performance tuning?

OpenTelemetry works with legacy monoliths by instrumenting them to emit traces and metrics. This integration enables performance tuning and capacity planning across hybrid environments, extending observability beyond microservices and containerized applications.

Why do I need distributed tracing and safe alerting configurations for incident detection?

Distributed tracing and safe alerting configurations are needed for real-time incident detection because they establish end-to-end observability across services. Tracing pinpoints performance bottlenecks while safe alerting rules prevent alert fatigue during capacity planning.

How to instrument applications with metrics and traces for capacity planning?

Instrument applications by configuring them to emit structured logs, metrics, and traces, then connect them to Prometheus or Grafana. Performing load testing and profiling alongside this instrumentation provides the data needed for accurate capacity forecasting and planning.