Skip to content
OpenSmartRoute
Skillv1.0.0

deploying-monitoring-stacks

Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog. Trigger with phrases like "deploy monitoring stack", "setup prometheus", "configure grafana", or "install datad

by jeremylongshore(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from jeremylongshore/tons-of-skills-marketplace (plugins/devops/monitoring-stack-deployer/skills/deploying-monitoring-stacks/SKILL.md). Install upstream with npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks. Copyright stays with the author (MIT).

Deploying Monitoring Stacks

Overview

Deploy production monitoring stacks (Prometheus + Grafana, Datadog, or Victoria Metrics) with metric collection, custom dashboards, and alerting rules. Configure exporters, scrape targets, recording rules, and notification channels for comprehensive infrastructure and application observability.

Prerequisites

  • Target infrastructure identified: Kubernetes cluster, Docker hosts, or bare-metal servers
  • Metric endpoints accessible from the monitoring platform (application /metrics, node exporters)
  • Storage backend capacity planned for time-series data (Prometheus TSDB, Thanos, or Cortex for long-term)
  • Alert notification channels defined: Slack webhook, PagerDuty integration key, or email SMTP
  • Helm 3+ for Kubernetes deployments using kube-prometheus-stack or similar charts

Instructions

  1. Select the monitoring platform: Prometheus + Grafana for open-source self-hosted, Datadog for managed SaaS, Victoria Metrics for high-cardinality workloads
  2. Deploy the monitoring stack: helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack or Docker Compose for non-Kubernetes
  3. Install exporters on monitored systems: node-exporter for host metrics, kube-state-metrics for Kubernetes object states, application-specific exporters
  4. Configure scrape targets in prometheus.yml: define job names, scrape intervals, and relabeling rules for service discovery
  5. Create recording rules for frequently queried aggregations to reduce dashboard query load
  6. Define alerting rules with meaningful thresholds: high CPU (>80% for 5m), high memory (>90%), error rate (>1%), latency P99 (>500ms)
  7. Configure Alertmanager with routing, grouping, and notification channels (Slack, PagerDuty, email)
  8. Build Grafana dashboards: RED metrics (Rate, Errors, Duration) for services, USE metrics (Utilization, Saturation, Errors) for resources
  9. Set up data retention: configure TSDB retention period (15-30 days local), set up Thanos/Cortex for long-term storage if needed
  10. Test the full pipeline: trigger a test alert and verify notification delivery

Output

  • Helm values file or Docker Compose for the monitoring stack
  • Prometheus configuration with scrape targets, recording rules, and alerting rules
  • Alertmanager configuration with routing tree and notification receivers
  • Grafana dashboard JSON files for infrastructure and application metrics
  • Exporter deployment manifests (node-exporter DaemonSet, application ServiceMonitor)

Error Handling

Error Cause Solution
No data points in dashboard Scrape target not reachable or metric name wrong Check Targets page in Prometheus UI; verify service discovery and metric name
Too many time series (high cardinality) Labels with unbounded values (user IDs, request IDs) Remove high-cardinality labels with metric_relabel_configs; use recording rules for aggregation
Alert condition met but no notification Alertmanager routing or receiver misconfigured Verify Alertmanager config with amtool check-config; test receiver with amtool silence
Prometheus OOMKilled Insufficient memory for series count Increase memory limits; reduce scrape targets or retention; add WAL compression
Grafana datasource connection failed Wrong Prometheus URL or network policy blocking access Verify datasource URL in Grafana; check Kubernetes service name and port; review network policies

Examples

  • "Deploy kube-prometheus-stack on Kubernetes with alerts for node CPU > 80%, pod restart count > 5, and API error rate > 1%, sending to Slack."
  • "Set up Prometheus + Grafana on Docker Compose for monitoring 10 application servers with node-exporter and custom application metrics."
  • "Create Grafana dashboards for the four golden signals (latency, traffic, errors, saturation) for a microservices application."

Resources

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/jeremylongshore-tons-of-skills-marketplace-deploying-mon-c3305d/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

jeremylongshore-tons-of-skills-marketplace-deploying-mon-c3305d.ocm.jsonjson
{
  "ocm": "1",
  "id": "jeremylongshore-tons-of-skills-marketplace-deploying-mon-c3305d",
  "kind": "skill",
  "name": "deploying-monitoring-stacks",
  "description": "Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog. Trigger with phrases like \"deploy monitoring stack\", \"setup prometheus\", \"configure grafana\", or \"install datadog agent\". Generates production-ready configurations with metric collection, visualization dashboards, and alerting rules.",
  "publisher": "jeremylongshore",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "devops",
      "deployment",
      "monitoring",
      "dashboard",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog. Trigger with phrases like \"deploy monitoring stack\", \"setup prometheus\", \"configure grafana\", or \"install datadog agent\". Generates production-ready configurations with metric collection, visualization dashboards, and alerting rules."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/jeremylongshore/tons-of-skills-marketplace",
      "path": "plugins/devops/monitoring-stack-deployer/skills/deploying-monitoring-stacks/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/HEAD/plugins/devops/monitoring-stack-deployer/skills/deploying-monitoring-stacks/SKILL.md",
      "key": "jeremylongshore/tons-of-skills-marketplace/plugins/devops/monitoring-stack-deployer/skills/deploying-monitoring-stacks/SKILL.md"
    },
    "compatibility": "Designed for Claude Code",
    "allowed_tools": [
      "Read,",
      "Write,",
      "Edit,",
      "Grep,",
      "Glob,",
      "Bash(docker:*),",
      "Bash(kubectl:*)"
    ],
    "license": "MIT"
  },
  "instructions": "# Deploying Monitoring Stacks\n\n## Overview\n\nDeploy production monitoring stacks (Prometheus + Grafana, Datadog, or Victoria Metrics) with metric collection, custom dashboards, and alerting rules. Configure exporters, scrape targets, recording rules, and notification channels for comprehensive infrastructure and application observability.\n\n## Prerequisites\n\n- Target infrastructure identified: Kubernetes cluster, Docker hosts, or bare-metal servers\n- Metric endpoints accessible from the monitoring platform (application `/metrics`, node exporters)\n- Storage backend capacity planned for time-serie",
  "cost": {
    "context_tokens": 1077
  }
}

Fetch it by URL: GET /api/v1/registry/jeremylongshore-tons-of-skills-marketplace-deploying-mon-c3305d/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.