Deploying Monitoring Stacks
FreeEffortlessly deploy monitoring solutions like Prometheus and Grafana.
Free · Opens the source repo
What Deploying Monitoring Stacks does
Deploying Monitoring Stacks is a skill designed for developers and DevOps engineers who need to set up and manage monitoring solutions for their applications and infrastructure. This skill focuses on deploying popular monitoring stacks such as Prometheus with Grafana, Datadog, or Victoria Metrics, providing users with the ability to collect metrics, visualize data through dashboards, and configure alerting rules effectively. It simplifies the process of getting a comprehensive observability solution up and running, which is crucial for maintaining system performance and reliability.
The skill guides users through the prerequisites necessary for deployment, including identifying the target infrastructure, ensuring metric endpoints are accessible, and planning for storage backend capacity. It also emphasizes the need for alert notification channels, which are essential for timely responses to system anomalies. Users can choose their preferred monitoring platform and follow detailed instructions to install the monitoring stack, configure exporters, set up scrape targets, and create alerting rules tailored to their specific requirements.
In addition to deployment, the skill generates production-ready configurations that include Prometheus configurations, Grafana dashboard JSON files, and Alertmanager settings. These outputs ensure that users have all the necessary components for effective monitoring right from the start. The skill also addresses common errors that may arise during setup, providing solutions to ensure a smooth deployment process.
This skill is particularly useful for teams looking to implement robust monitoring solutions in cloud-native environments, such as Kubernetes or Docker, as well as on bare-metal servers. It is suitable for both new users who require step-by-step guidance and experienced practitioners who want to streamline their monitoring stack deployments.
When to use it
Use this skill when you need to deploy a monitoring stack for your applications or infrastructure and require a structured approach to configuration and setup.
When not to use it
This skill may not be suitable for users who are looking for a fully managed monitoring solution without any setup, as it requires some configuration and deployment steps.
What you can build with it
Kubernetes Monitoring Setup
Deploy kube-prometheus-stack on a Kubernetes cluster with alerts configured for high CPU usage and pod restarts.
Docker Monitoring for Applications
Set up Prometheus and Grafana on Docker Compose to monitor multiple application servers with custom metrics.
Creating Custom Dashboards
Use the skill to build Grafana dashboards that visualize key performance indicators for a microservices architecture.
How to install Deploying Monitoring Stacks
View source1. Install with the skills CLI
npx skills add jeremylongshore/claude-code-plugins-plus-skills/deploying-monitoring-stacks --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by jeremylongshoreDeploying 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
- Select the monitoring platform: Prometheus + Grafana for open-source self-hosted, Datadog for managed SaaS, Victoria Metrics for high-cardinality workloads
- Deploy the monitoring stack:
helm install kube-prometheus-stack prometheus-community/kube-prometheus-stackor Docker Compose for non-Kubernetes - Install exporters on monitored systems: node-exporter for host metrics, kube-state-metrics for Kubernetes object states, application-specific exporters
- Configure scrape targets in
prometheus.yml: define job names, scrape intervals, and relabeling rules for service discovery - Create recording rules for frequently queried aggregations to reduce dashboard query load
- Define alerting rules with meaningful thresholds: high CPU (>80% for 5m), high memory (>90%), error rate (>1%), latency P99 (>500ms)
- Configure Alertmanager with routing, grouping, and notification channels (Slack, PagerDuty, email)
- Build Grafana dashboards: RED metrics (Rate, Errors, Duration) for services, USE metrics (Utilization, Saturation, Errors) for resources
- Set up data retention: configure TSDB retention period (15-30 days local), set up Thanos/Cortex for long-term storage if needed
- 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
- Prometheus documentation: https://prometheus.io/docs/
- Grafana documentation: https://grafana.com/docs/grafana/latest/
- kube-prometheus-stack: https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack
- Alerting best practices: https://prometheus.io/docs/practices/alerting/
- Datadog documentation: https://docs.datadoghq.com/
Frequently asked questions about Deploying Monitoring Stacks
Similar skills
Turborepo
Optimized build system for JavaScript/TypeScript monorepos.
Azure Pipelines Validation
Streamline your Azure DevOps pipeline changes locally.
Azure Developer CLI
Streamline your Azure project workflows with best practices.
Azure Container Registry CLI
Manage Azure Container Registry resources with ease.
Aspire
Build and orchestrate polyglot distributed applications seamlessly.
Vercel CLI
Manage and deploy Vercel projects from the command line.