Skip to content

Repository files navigation

788+ production-ready Prometheus alerting rules for 80+ services — just copy-paste YAML

Ready-to-use Prometheus alert rules for various components. All .yml files are valid rules to include via rule_files.

Prometheus

Prometheus self-monitoring

Observability

Logging

Docker Containers

cAdvisor

Container runtimes

Databases

Brokers

Proxies and load balancers

Runtimes

Data engineering

Orchestrators

CI/CD

Host monitoring

Virtualization

Network and security

Storage

Security

How to use

Add the rules you need to rule_files in the Prometheus config:

rule_files:
  - databases/mysql.yml
  - proxy/haproxy.yml

Releases

Rules are frozen into versioned releases. Each release is tagged vX.Y.Z and described in CHANGELOG.md. Pin rules to a tag for reproducibility:

https://raw.githubusercontent.com/philyuchkoff/prometheus-alerts/<tag>/databases/mysql.yml

Create a new release manually via GitHub Releases or via git tag vX.Y.Z && git push --tags.

CI

Every PR and push to master runs promtool check rules against all rule files and promtool test rules for unit tests (see .github/workflows/validate.yml).

Tests

Expressions are covered by unit tests (promtool test rules format) in the tests/ directory:

promtool test rules tests/prometheus-test.yml
promtool test rules tests/mysql-test.yml
promtool test rules tests/podman-test.yml

To keep CI green for a new rules file, add a matching tests/<name>-test.yml.

Attribution

Part of the rules are adapted from samber/awesome-prometheus-alerts (CC BY 4.0):

Each of these files also carries an attribution header pointing to the original source.

License

Licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0).

About

Collection of some useful Prometheus alerting rules

Topics

Resources

Stars

25 stars

Watchers

1 watching

Forks

Contributors