Prometheus Configuration

by wshobson46891e7e60daNo licenseListed Oct 8, 2026Updated Oct 8, 2026

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.

Instructions onlyDevOps & Cloud
AI-generated overview

Guides Prometheus setup for metric collection, scrape configuration, recording rules, and alerting.

What it does
Provides a configuration guide for Prometheus covering metric collection, scrape configuration, recording rules, and alert rule design. It includes best practices for naming, scrape intervals, retention, relabeling, high availability, federation, and long-term storage. It also lists troubleshooting commands for checking targets, configuration, and queries, and points to a reference file for detailed patterns.
When to use it
Use when setting up Prometheus monitoring, configuring metric scraping, creating recording rules, designing alert rules, or implementing service discovery.
Requirements
No scripts; instructions only. Requires a Prometheus instance and network access to its HTTP API for the troubleshooting commands.

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

Source and attribution

Source:wshobson/agentsinplugins/observability-monitoring/skills/prometheus-configurationat commit46891e7

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal