Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

monitoring-instrumentation | devops-practices

Home
Skills
devops-practices
monitoring-instrumentation

Skill

monitoring-instrumentation

From devops-practices

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

Popularity

Parent stars

13

Parent forks

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/devops-practices:monitoring-instrumentation

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Observing systems to understand behavior and detect problems.

SKILL.md

45 lines · ~368 tokens

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

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

Define SLOs: Service level objectives; what matters?
Metrics: Latency, error rate, throughput; per service/endpoint
Logs: Structured logs with trace ID for correlation
Traces: End-to-end request tracking for debugging
Dashboards: Visualize SLOs; use during incident response
Alerts: Alert on SLO violations, not absolute thresholds
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)

$

npx claudepluginhub sethdford/claude-skills --plugin engineer-devops-practices

Similar Skills

monitoring-ops

24

Provides observability patterns for metrics, logging, tracing, alerting, dashboards, and infrastructure monitoring in production systems with Prometheus, Grafana, OpenTelemetry.

4 files3 tools

View monitoring-ops

observability-engineer

41.7k

Designs production-grade monitoring, logging, and tracing systems with SLI/SLO management, alerting, and incident response workflows.

antigravity-awesome-skills

View observability-engineer

monitoring-strategy

13

Design monitoring and alerting that catches production issues fast without creating alert fatigue. Use when establishing observability or improving incident response.

engineering-excellence

View monitoring-strategy