Monitoring Instrumentation
Metrics, logs, traces (observability); choosing what to measure, dashboards, and incident response.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill monitoring-instrumentationgit 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-instrumentationPersonal 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)
Details
- Skill name
monitoring-instrumentation- Repository
- sethdford/claude-skills
- 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
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Observability Design
48sethdford/claude-skills
Design observability (metrics, logs, traces) for understanding system behavior in production. Use when debugging distributed systems or building monitoring.
Migration Strategy
48sethdford/claude-skills
Safe schema migrations, backward compatibility, zero-downtime deployments, and rollback strategies.
Service Mesh Patterns
48sethdford/claude-skills
Implement service mesh patterns for observability, resilience, and traffic management. Use when managing complex microservices communication at scale.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.