Showing 28 verified skills. 284 preview entries are hidden until we confirm a real source. Show preview skills · Why?
Set up Prometheus, Grafana, and alerting in one go
claude install community/monitoring-setupFull observability setup: configure Prometheus metrics, build Grafana dashboards, define alerting rules, and establish SLI/SLO targets.
This is the actual SKILL.md file that powers this skill. Copy it to install.
---
name: monitoring-setup
description: |
Trigger when the user asks to add monitoring, observability, metrics, or
error tracking. Phrases: "set up Sentry", "add monitoring", "observability",
"OpenTelemetry", "add metrics", "error tracking".
allowed-tools:
- Bash(npm install *)
- Bash(pnpm add *)
- Read
- Write
- Edit
---
# Monitoring Setup
Add the three-legged observability stack (errors, logs, metrics) with the
minimum viable config. Focus on signals that actually page someone.
## Prerequisites
- Production target identified (Vercel, Coolify, Fly, AWS, etc.)
- Stack known (Node, Python, etc.)
## Steps
1. **Errors first: Sentry.** Most bang for the buck in 24 hours of setup.
```bash
pnpm add @sentry/nextjs
npx @sentry/wizard@latest -i nextjs
```
2. **Set release tracking.** Sentry groups errors by release. Wire the release
to the git SHA via env var:
```
SENTRY_RELEASE=${VERCEL_GIT_COMMIT_SHA}
```
3. **Add one alert that wakes someone.** In Sentry: new-issue alert on
production. Target: PagerDuty, Slack #oncall, or email.
4. **Logs next: structured JSON to stdout.** Let the platform collect. In Node:
```ts
import { pino } from "pino";
export const log = pino({ level: "info" });
```
Replace `console.log` with structured log calls:
```ts
log.info({ userId, route }, "user signed in");
```
5. **Metrics last: OpenTelemetry for traces, Prometheus scrape for counters.**
For a small app, skip Prometheus and use OpenTelemetry traces only.
```bash
pnpm add @opentelemetry/sdk-node @opentelemetry/auto-instrumentations-node
```
6. **Hook up a dashboard.** Honeycomb, Datadog, or Grafana. One dashboard
with four tiles: error rate, p95 latency, request rate, saturation.
## What not to do
- Do not set up 17 dashboards no one looks at.
- Do not log every request body at info level. PII and volume costs.
- Do not alert on every warning. Alerts that do not wake someone train people
to ignore alerts.
## Output
- Sentry configured with release + one alert
- Structured logging in place, console.log grepped and migrated
- OpenTelemetry traces to at least one collector
- Dashboard with 4 core tiles
mkdir -p ~/.claude/skills/monitoring-setup~/.claude/skills/monitoring-setup/SKILL.mdResulting file structure:
~/.claude/
skills/
monitoring-setup/
SKILL.md <-- skill definitionSkills are loaded automatically by Claude Code when you start a new session. The skill name and description in the frontmatter determine when Claude triggers it.
Recommended from shared domain, career, and tool overlap with Monitoring Setup
Manage DNS records and domain migrations with zero-downtime plans
Both used by DevOps Engineer
Find the needle in your logs - pattern detection and root cause analysis
Both used by DevOps Engineer
Track SLOs with error budget burn rates and compliance reports
Both used by DevOps Engineer
Monitor webhook delivery rates and catch failures before customers do
Both used by DevOps Engineer
Generate Kubernetes manifests and Helm charts from your app specs
Both used by DevOps Engineer
Manage AWS resources - S3, Lambda, and CloudWatch - from your editor
Both used by DevOps Engineer
Monitoring Setup