Index of every page on this site: llms.txt
All skills
Run it yourself

Build real-time API monitoring dashboards with metrics, alerts, and health checks. Use when tracking API health and performance metrics. Trigger with phrases like "monitor the API", "add API metrics", or "setup API monitoring".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/monitoring-apis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈61 tokens for metadata: the name and description. ≈1.3k when used: this file. ≈2k more on demand in 3 files.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈245 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Monitoring APIs

Overview

Build real-time API monitoring with metrics collection (request rate, latency percentiles, error rates), health check endpoints, and alerting rules. Instrument API middleware to emit Prometheus metrics or StatsD counters, configure Grafana dashboards with SLO tracking, and implement synthetic monitoring probes for uptime verification.

Prerequisites

  • Prometheus + Grafana stack, or Datadog/New Relic/CloudWatch for metrics and dashboards
  • Metrics client library: prom-client (Node.js), prometheus_client (Python), or Micrometer (Java)
  • Alerting channel configured: PagerDuty, Slack webhook, or email for alert routing
  • Structured logging library: Winston, Pino (Node.js), structlog (Python), or Logback (Java)
  • Synthetic monitoring tool: Checkly, Uptime Robot, or custom cron-based health probes

Instructions

  1. Examine existing middleware and logging setup using Grep and Read to identify current observability coverage and gaps.
  2. Implement metrics middleware that records per-request data: http_request_duration_seconds histogram (with method, path, status labels), http_requests_total counter, and http_requests_in_flight gauge.
  3. Create a /health endpoint returning structured health status including dependency checks (database connectivity, cache availability, external service reachability) with response time for each.
  4. Add a /ready endpoint separate from health that returns 503 during startup initialization and graceful shutdown, for load balancer integration.
  5. Configure histogram buckets aligned with SLO targets: [0.01, 0.05, 0.1, 0.25, 0.5, 1, 2.5, 5, 10] seconds for comprehensive latency distribution.
  6. Build Grafana dashboard panels: request rate (QPS), p50/p95/p99 latency, error rate percentage, active connections, and per-endpoint breakdown.
  7. Define alerting rules: error rate > 5% for 5 minutes (critical), p99 latency > 2s for 10 minutes (warning), health check failure for 3 consecutive probes (critical).
  8. Implement synthetic monitoring that sends periodic requests to critical endpoints from external locations, measuring availability and latency from the consumer perspective.
  9. Add SLO tracking with error budget calculation: define SLO (99.9% availability, p95 < 500ms), compute burn rate, and alert when error budget consumption exceeds projected pace.

See references/implementation.md for the full implementation guide.

Output

  • ${CLAUDE_SKILL_DIR}/src/middleware/metrics.js - Prometheus metrics collection middleware
  • ${CLAUDE_SKILL_DIR}/src/routes/health.js - Health check and readiness endpoints
  • ${CLAUDE_SKILL_DIR}/monitoring/dashboards/ - Grafana dashboard JSON definitions
  • ${CLAUDE_SKILL_DIR}/monitoring/alerts/ - Alerting rule definitions (Prometheus AlertManager or Grafana)
  • ${CLAUDE_SKILL_DIR}/monitoring/synthetic/ - Synthetic monitoring probe scripts
  • ${CLAUDE_SKILL_DIR}/monitoring/slo.yaml - SLO definitions and error budget configuration

Error Handling

Error Cause Solution
Metrics cardinality explosion High-cardinality labels (user ID, request ID) on metrics Use bounded label values only (method, status code, endpoint group); aggregate user-level data in logs
Health check false positive Health endpoint returns 200 but dependent service is degraded Include dependency checks with individual status; use structured response with degraded state
Alert fatigue Too many low-severity alerts firing during normal operations Tune alert thresholds using historical baselines; implement alert grouping and deduplication
Dashboard data gap Metrics not collected during deployment rollout window Configure Prometheus scrape interval < deployment duration; use push-based metrics during deploys
SLO miscalculation Error budget calculation uses wrong time window or includes planned maintenance Exclude maintenance windows from SLO calculation; align window with business reporting period

Refer to references/errors.md for comprehensive error patterns.

Examples

RED method dashboard: Request rate, Error rate, and Duration panels per endpoint, with drill-down from overview to individual endpoint detail, including top-10 slowest endpoints by p99.

SLO-based alerting: Define 99.9% availability SLO with 30-day rolling window, alert when 1-hour burn rate exceeds 14.4x (consuming daily error budget in 1 hour), with PagerDuty escalation.

Dependency health matrix: Dashboard showing real-time health status of all downstream dependencies (database, cache, external APIs) with latency sparklines and circuit breaker state indicators.

See references/examples.md for additional examples.

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is safe to use. It provides standard templates and instructions for implementing API monitoring, health checks, and alerting using well-known libraries like Prometheus and Grafana. No malicious patterns or security vulnerabilities were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated last month
What it can do
Reads files Edits files Runs commands
version
1.26.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "api",
  "monitoring",
  "performance",
  "dashboard"
]
All 6 allowed tools
ReadWriteEditGrepGlobBash(api:monitor-*)
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/monitoring-apis