Waymark / Routes / prometheus.io Write Prometheus recording rules and alerting rules with for and keep_firing_for clauses
domain: prometheus.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Create a rule group file with recording rules that pre-aggregate expensive PromQL expressions into new metric series Write alerting rules with threshold expressions and set the for duration to require the condition to persist before firing Add a keep_firing_for duration to prevent the alert from resolving immediately when the condition briefly dips below the threshold Add labels and annotations to alerting rules to route them correctly in Alertmanager and provide runbook links Load the rule file into Prometheus and validate it using the promtool check rules subcommand before deploying Known gotchas Recording rule metric names should follow the naming convention that encodes the aggregation to avoid confusion with raw metrics The for duration resets if the alert condition disappears and reappears; a flapping metric can delay alert firing indefinitely without keep_firing_for Rule group evaluation intervals that are shorter than the scrape interval can produce gaps in recording rule output when scrape data is missing
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp