skilld
All skills
wshobson avatar

/prometheus-configuration

@be57c0b
by Seth Hobsonwshobson/agents40k stars
4,281

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/wshobson/agents/prometheus-configuration

This session only. Nothing lands on disk.

SKILL.md

≈63 tokens always: the name and description. ≈379 when used: this file. ≈2.1k more on demand in 1 file.

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

Source: SKILL.md on GitHub

Third-party checks

2 warnings1d5 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides standard and secure guidance for configuring Prometheus monitoring. It includes configuration templates, best practices, and installation steps using well-known tools like Helm and Docker Compose. All external resources point to trusted community repositories and the provided commands are for local diagnostic purposes.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: MEDIUM · 1 issue

  • Runlayer6mo

    1/1 file flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

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

Last checked against GitHub 3 days ago.

Activeupdated 4 months ago

Topics

  • Infrastructure
  • prometheus
  • monitoring
  • metrics
  • alerting
  • scrape-config
  • recording-rules
  • service-discovery

README badge

README badge for wshobson/agents/prometheus-configuration

What it does

Configures Prometheus for metric collection, scrape targets, and alerting rules across infrastructure and applications. Covers scrape intervals, recording rules, relabeling, high availability setup, and retention policies.

Generated from the current SKILL.md.

Frequently asked

Does this skill cover alert rule configuration?
Yes. The skill includes designing alert rules as part of comprehensive Prometheus setup, though detailed patterns are documented in references/details.md.
What scrape intervals does this skill recommend?
The skill recommends typical scrape intervals of 15-60 seconds, with guidance on setting appropriate intervals based on your monitoring needs.
Does this skill address high availability setups?
Yes. High availability with multiple Prometheus instances is listed as a best practice, along with federation for large deployments and Thanos/Cortex for long-term storage.
What metrics naming convention does this skill use?
The skill recommends consistent naming using the format prefix_name_unit for all metrics.

Generated from the current SKILL.md. These answers refresh after source changes.