monitoring-expert

Configure monitoring and observability pipelines with Prometheus, Grafana, and OpenTelemetry.

2|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill monitoring-expert-rabbicse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-expert
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/monitoring-expert
Command: npx skills add https://github.com/rabbicse/go-projects --skill monitoring-expert-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from production support by turning opaque services into observable systems with logs, metrics, traces, alerts, and performance signals.

Core Features & Use Cases

  • Structured Logging: Design JSON logging pipelines with request IDs and safe field redaction for production troubleshooting.
  • Metrics and Dashboards: Instrument services with Prometheus metrics and build Grafana views for latency, error rate, throughput, and business KPIs.
  • Alerting and Tracing: Define actionable Prometheus alerts, wire in OpenTelemetry tracing, and correlate events across distributed services.
  • Performance Engineering: Plan and run load tests, profile CPU and memory bottlenecks, and forecast capacity for growth.
  • Use Case: A backend team can use this Skill to diagnose a slow checkout path, trace the failing dependency, create alerts for error spikes, and validate the fix under load.

Quick Start

Use this Skill to design monitoring for a Go service by adding structured logs, Prometheus metrics, Grafana dashboards, alerting rules, and tracing instrumentation.

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 Prometheus metrics and Grafana dashboards for my backend service?

To set up Prometheus metrics and Grafana dashboards, you instrument backend services to expose metrics, configure Prometheus to scrape them, and build Grafana views for latency, error rate, throughput, and business KPIs.

What is the best way to design structured logging for production troubleshooting?

The best way to design structured logging for production troubleshooting is creating JSON logging pipelines that include request IDs and apply safe field redaction to protect sensitive data.

How do I trace a failing dependency in a distributed system?

To trace a failing dependency in a distributed system, you wire in OpenTelemetry tracing instrumentation to correlate events across distributed services, isolating the bottleneck.

Can I use this approach to forecast capacity and plan for infrastructure growth?

Yes, you can forecast capacity for growth by profiling CPU and memory bottlenecks, running load tests, and analyzing performance signals to predict future resource requirements.

How do I create actionable alerts for error spikes in production?

You create actionable alerts for error spikes by defining Prometheus alert rules that trigger based on specific metric thresholds, ensuring teams are notified of production issues.

Do I need OpenTelemetry to implement distributed tracing and health checks?

You need OpenTelemetry to implement distributed tracing and correlate events across services, while health checks can be configured independently to monitor service availability.