monitoring-setup

Design and implement observability stacks with Prometheus, Grafana, Loki, and Jaeger.

4|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xcrrr/claude-skills --skill monitoring-setup-xcrrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-setup
Source: https://github.com/xcrrr/claude-skills/tree/main/skills/devops/monitoring-setup
Command: npx skills add https://github.com/xcrrr/claude-skills --skill monitoring-setup-xcrrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability design and implementation for production systems to gain full visibility across metrics, logs, and traces.

Core Features & Use Cases

  • Instrument services with metrics, logs, and traces (Prometheus, Grafana, Loki, Jaeger)
  • Define SLIs/SLOs and burn-rate alerting to manage reliability
  • Build dashboards and alerting pipelines to detect and respond to incidents
  • Apply runbooks and structured logging to reduce MTTR in production

Quick Start

Design and implement a starter observability stack for a new service, wiring Prometheus metrics, Grafana dashboards, Loki logs, and Jaeger traces.

Frequently Asked Questions about monitoring-setup

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

FAQPage Schema
How do I build an end-to-end observability stack with Prometheus and Grafana?

To build an end-to-end observability stack, you instrument services with Prometheus metrics, Grafana dashboards, Loki logs, and Jaeger traces to gain full production visibility and reduce MTTR.

How do I define SLIs and SLOs for burn-rate alerting?

Defining SLIs and SLOs involves setting reliability targets and configuring burn-rate alerting in Prometheus to manage service reliability and detect incidents before error budgets are exhausted.

Can I add Loki logging and Jaeger tracing to existing services?

You can integrate Loki logging and Jaeger tracing into existing services by configuring structured logging pipelines and trace instrumentation alongside current Prometheus metrics scrape targets.

What is the best way to configure Prometheus scrape targets and alert rules?

The best way to configure Prometheus scrape targets and alert rules is to define metric collection endpoints and write explicit alert rules to provision dashboards and detect production anomalies.

Do I need structured logging and runbooks to reduce MTTR in production?

You need structured logging pipelines and runbooks to reduce MTTR because they provide contextual Loki logs and guided incident response steps for faster troubleshooting when alerts trigger.