Monitoring Instrumentation

Metrics, logs, traces (observability); choosing what to measure, dashboards, and incident response.

48 stars 10 forksDevOps & Cloud Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill monitoring-instrumentation
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/devops-practices/skills/monitoring-instrumentation ~/.claude/skills/monitoring-instrumentation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Monitoring Instrumentation

Observing systems to understand behavior and detect problems.

## Context

You are planning observability. Measure what matters; enable debugging.

## Domain Context

- **Metrics**: Numbers (latency, errors, CPU); aggregated, queryable
- **Logs**: Text events; detailed, high volume
- **Traces**: Request paths; understand where time is spent
- **Dashboards**: Visualize metrics for on-call engineers
- **Alerts**: Notify when metrics exceed thresholds

## Instructions

1. **Define SLOs**: Service level objectives; what matters?
2. **Metrics**: Latency, error rate, throughput; per service/endpoint
3. **Logs**: Structured logs with trace ID for correlation
4. **Traces**: End-to-end request tracking for debugging
5. **Dashboards**: Visualize SLOs; use during incident response
6. **Alerts**: Alert on SLO violations, not absolute thresholds
7. **Runbooks**: Document how to respond to alerts

## Anti-Patterns

- Too many metrics; noisy, hard to find signal
- Alerts with no runbook; on-call engineer guesses
- Logging everything; expensive and hard to search
- No trace IDs; can't correlate across services
- Alerting on absolute thresholds; SLO-based is better

## Further Reading

- Google SRE book on monitoring
- Prometheus documentation
- Distributed tracing (Jaeger, DataDog)
Read the full skill on GitHub

Details

Skill name
monitoring-instrumentation
Path
engineer/devops-practices/skills/monitoring-instrumentation/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Monitoring Instrumentation skill do?

Metrics, logs, traces (observability); choosing what to measure, dashboards, and incident response.

How do I install the Monitoring Instrumentation skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Monitoring Instrumentation popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.