prometheus-configuration
wshobson/agents
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications.
What is prometheus-configuration?
Prometheus Configuration provides guidance for setting up Prometheus to collect metrics, store time-series data, and implement alerting across infrastructure and applications. Use this when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
- Configure metric scraping from targets with appropriate intervals
- Create recording rules for expensive queries and metric aggregation
- Design alert rules for infrastructure and application monitoring
- Implement service discovery for dynamic target management
- Set up metric retention policies based on storage capacity
- Use relabeling for metric cleanup and standardization
How to install prometheus-configuration
npx skills add https://github.com/wshobson/agents --skill prometheus-configuration- Prometheus server installed and running
- Understanding of metric naming conventions
- Access to targets that expose metrics endpoints
- Basic knowledge of PromQL (Prometheus Query Language)
How to use prometheus-configuration
- 1.Define scrape targets in prometheus.yml with appropriate intervals (15-60s typical)
- 2.Configure relabeling rules to clean up and standardize metric names
- 3.Create recording rules for frequently-used or expensive queries
- 4.Design alert rules with clear thresholds and notification channels
- 5.Implement service discovery if managing dynamic infrastructure
- 6.Monitor Prometheus itself to ensure reliability
- 7.Test queries using the Prometheus API or web UI
Use cases
- Setting up monitoring for microservices infrastructure
- Configuring Prometheus to scrape metrics from multiple application instances
- Creating recording rules to pre-compute expensive aggregations
- Implementing alerting rules for SLO violations and system anomalies
- Designing high-availability Prometheus deployments with federation
- DevOps engineers
- Site reliability engineers (SREs)
- Infrastructure architects
- Application developers implementing observability
- Platform teams managing monitoring infrastructure
prometheus-configuration FAQ
Typical scrape intervals range from 15-60 seconds depending on your needs; shorter intervals provide more granularity but increase storage and CPU usage.
Use curl http://localhost:9090/api/v1/targets to view all targets and their scrape status.
Use recording rules to pre-compute expensive queries that run frequently, reducing query latency and Prometheus CPU usage.
Run multiple Prometheus instances scraping the same targets, then use federation or tools like Thanos/Cortex for deduplication and long-term storage.
Configure retention based on your storage capacity and query needs; typical values range from 15 days to several months.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
name: prometheus-configuration description: Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
Prometheus Configuration
Complete guide to Prometheus setup, metric collection, scrape configuration, and recording rules.
Purpose
Configure Prometheus for comprehensive metric collection, alerting, and monitoring of infrastructure and applications.
When to Use
- Set up Prometheus monitoring
- Configure metric scraping
- Create recording rules
- Design alert rules
- Implement service discovery
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
Best Practices
- Use consistent naming for metrics (prefix_name_unit)
- Set appropriate scrape intervals (15-60s typical)
- Use recording rules for expensive queries
- Implement high availability (multiple Prometheus instances)
- Configure retention based on storage capacity
- Use relabeling for metric cleanup
- Monitor Prometheus itself
- Implement federation for large deployments
- Use Thanos/Cortex for long-term storage
- Document custom metrics
Troubleshooting
Check scrape targets:
curl http://localhost:9090/api/v1/targets
Check configuration:
curl http://localhost:9090/api/v1/status/config
Test query:
curl 'http://localhost:9090/api/v1/query?query=up'
Related Skills
grafana-dashboards- For visualizationslo-implementation- For SLO monitoringdistributed-tracing- For request tracing
Related skills
More from wshobson/agents and the wider catalog.
prompt-engineering-patterns
Master advanced prompt engineering techniques to maximize LLM performance and reliability.
protect-mcp-setup
Cryptographic policy enforcement and Ed25519-signed audit receipts for Claude Code tool calls.
protocol-reverse-engineering
Capture, analyze, and document network protocols for security research and debugging.
python-anti-patterns
Checklist of common Python anti-patterns to catch before code review and deployment.
python-background-jobs
Async task queues and background job patterns for decoupling long-running work from request/response cycles.
python-code-style
Modern Python linting, formatting, type checking, and documentation standards with ruff, mypy, and Google-style docstrings.