Skill

monitoring-observability

Monitoring and observability patterns. Prometheus RED/USE metrics, structured logging with Pino/Winston, OpenTelemetry tracing, SLO-based alerting, Grafana dashboards, burn rate alerts.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

Use when setting up metrics, logging, tracing, or alerting for services. Covers the three pillars of observability, SLO definition, dashboard design, and alert fatigue prevention.

Supporting Assets

assets/alert-rules-template.yamlassets/grafana-dashboard-template.jsonreferences/alerting-strategies.mdreferences/logging-patterns.mdreferences/metrics-patterns.mdreferences/tracing-patterns.md

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

gateguard

Blocks Edit/Write/Bash (including MultiEdit) until investigating importers via Grep, data schemas, affected functions, and user instructions verbatim. Improves output quality in multi-module codebases.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

Core principles

Three pillars: logs, metrics, traces — each answers different questions

Structured logging always — JSON logs are searchable; free-text logs are archaeology

RED method for services — Rate, Errors, Duration per endpoint

SLO-based alerting — alert on burn rate, not raw error count

Correlation IDs through every hop — without them, distributed debugging is guesswork

References available

references/metrics-patterns.md — RED/USE methods, Prometheus counters/histograms/gauges, Grafana dashboards

references/logging-patterns.md — Structured logging (Pino/Winston), levels, aggregation (ELK/Loki), correlation IDs

references/tracing-patterns.md — OpenTelemetry setup, span design, sampling strategies, trace analysis

references/alerting-strategies.md — SLO-based alerting, burn rate (14.4x fast, 6x slow), alert fatigue prevention

Monitoring & Observability

When to use

Use when setting up metrics, logging, tracing, or alerting for services. Covers the three pillars of observability, SLO definition, dashboard design, and alert fatigue prevention.

Core principles

Three pillars: logs, metrics, traces — each answers different questions
Structured logging always — JSON logs are searchable; free-text logs are archaeology
RED method for services — Rate, Errors, Duration per endpoint
SLO-based alerting — alert on burn rate, not raw error count
Correlation IDs through every hop — without them, distributed debugging is guesswork

References available

references/metrics-patterns.md — RED/USE methods, Prometheus counters/histograms/gauges, Grafana dashboards
references/logging-patterns.md — Structured logging (Pino/Winston), levels, aggregation (ELK/Loki), correlation IDs
references/tracing-patterns.md — OpenTelemetry setup, span design, sampling strategies, trace analysis
references/alerting-strategies.md — SLO-based alerting, burn rate (14.4x fast, 6x slow), alert fatigue prevention

Assets available

assets/grafana-dashboard-template.json — Starter RED metrics dashboard
assets/alert-rules-template.yaml — Prometheus alert rules for SLO burn rate