Index of every page on this site: llms.txt
All skills
wshobson avatar

/prometheus-configuration

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

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.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

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

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈254 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning18d5 checks · Risk SAFE
  • Gen Agent Trust Hub18d

    This skill provides standard documentation and configuration examples for setting up Prometheus monitoring. It includes Helm commands, Docker Compose configurations, and Prometheus rule examples. No security issues were detected.

  • Socket1mo

    No alerts

  • Snyk18d

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4220308. 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 6 months ago
  • Infrastructure
  • prometheus
  • monitoring
  • metrics
  • alerting
  • scrape-config
  • recording-rules
  • service-discovery

README badge

README badge for wshobson/agents/prometheus-configuration

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.

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.