monitoring-patterns

Configure Prometheus scrape configs, Grafana dashboards, and SLO/SLI alerting patterns.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/bipinks/ghost-office --skill monitoring-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-patterns
Source: https://github.com/bipinks/ghost-office/tree/main/.claude/skills/monitoring-patterns
Command: npx skills add https://github.com/bipinks/ghost-office --skill monitoring-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge base provides ready-made patterns for instrumenting services, collecting metrics with Prometheus, and setting up robust alerting and dashboards to reduce MTTR and improve reliability.

Core Features & Use Cases

  • Prometheus configuration patterns for service discovery, scrape intervals, and relabeling
  • Alert rules and runbooks aligned with four golden signals, SLO/SLI definitions, and error budgets
  • Grafana dashboards and JSON models for service overview, latency decomposition, and health monitoring
  • Best practices for labeling, retention, and on-call readiness across environments

Quick Start

Configure a Prometheus scrape for a target service, wire up alert rules, and import the Grafana dashboard model to begin monitoring.

Frequently Asked Questions about monitoring-patterns

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

FAQPage Schema
How do I configure Prometheus scrape configs for service discovery and relabeling?

Prometheus scrape configurations are set up using service discovery mechanisms to automatically find targets, adjust scrape intervals, and apply relabeling rules to standardize metrics collection across distributed environments.

What is the best way to define SLOs and error budgets for alerting?

Defining SLOs and error budgets involves creating alert rules aligned with the four golden signals and SLI definitions, ensuring your alerting setup accurately tracks service reliability and reduces mean time to recovery.

Can I use Grafana dashboards to monitor latency and service health?

Grafana dashboards can be imported using JSON models to monitor service overviews, decompose latency metrics, and visualize overall health, providing robust observability across multiple deployment environments.

Does this monitoring pattern support distributed systems across multiple environments?

These observability patterns apply directly to distributed systems, providing end-to-end metrics collection, alerting, and dashboard configurations tailored for services running across multiple environments.

How do I set up on-call readiness and alerting best practices?

On-call readiness requires establishing best practices for metric labeling, data retention, and alert rule configurations paired with runbooks to ensure reliable incident response and system observability.