Claude Cursor Skill

prometheus-configuration

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.

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_observability-monitoring_skills_prometheus-configuration-46891e7.zip · 3 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/observability-monitoring/skills/prometheus-configuration
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

  1. Use consistent naming for metrics (prefix_name_unit)
  2. Set appropriate scrape intervals (15-60s typical)
  3. Use recording rules for expensive queries
  4. Implement high availability (multiple Prometheus instances)
  5. Configure retention based on storage capacity
  6. Use relabeling for metric cleanup
  7. Monitor Prometheus itself
  8. Implement federation for large deployments
  9. Use Thanos/Cortex for long-term storage
  10. 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 visualization
  • slo-implementation - For SLO monitoring
  • distributed-tracing - For request tracing
Files (agents)
  • references
    • details.md 8.1 KB
      Loading…
  • SKILL.md 1.8 KB
    ---
    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
    
    1. **Use consistent naming** for metrics (prefix_name_unit)
    2. **Set appropriate scrape intervals** (15-60s typical)
    3. **Use recording rules** for expensive queries
    4. **Implement high availability** (multiple Prometheus instances)
    5. **Configure retention** based on storage capacity
    6. **Use relabeling** for metric cleanup
    7. **Monitor Prometheus itself**
    8. **Implement federation** for large deployments
    9. **Use Thanos/Cortex** for long-term storage
    10. **Document custom metrics**
    
    ## Troubleshooting
    
    **Check scrape targets:**
    
    ```bash
    curl http://localhost:9090/api/v1/targets
    ```
    
    **Check configuration:**
    
    ```bash
    curl http://localhost:9090/api/v1/status/config
    ```
    
    **Test query:**
    
    ```bash
    curl 'http://localhost:9090/api/v1/query?query=up'
    ```
    
    
    ## Related Skills
    
    - `grafana-dashboards` - For visualization
    - `slo-implementation` - For SLO monitoring
    - `distributed-tracing` - For request tracing
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.