Complete PromQL toolkit with generation and validation capabilities
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
{
"context": "Tests whether the agent writes alerting rules with for clauses, replaces increase() with rate() in alert expressions, and implements a multi-window burn-rate alert using both a short and long window combined with 'and'.",
"type": "weighted_checklist",
"checklist": [
{
"name": "for clause on all alerts",
"description": "Every alert rule in the file includes a 'for:' clause — no alert rule is missing it",
"max_score": 18
},
{
"name": "rate() not increase() in alert expr",
"description": "The corrected high-error alert uses rate() in its expr, not increase()",
"max_score": 15
},
{
"name": "Multi-window alert present",
"description": "An alert rule uses 'and' to combine two separate window conditions (one long window e.g. 1h, one short window e.g. 5m)",
"max_score": 15
},
{
"name": "Burn rate multiplier applied",
"description": "The burn-rate alert expression includes a burn rate factor (e.g., 14.4 or similar multiplier) relative to the error budget",
"max_score": 12
},
{
"name": "job label filter present",
"description": "Alert expressions include a job label filter (e.g., {job=\"checkout\"})",
"max_score": 8
},
{
"name": "rate() per-second threshold in corrected alert",
"description": "The corrected alert threshold is expressed as a per-second rate value (a decimal < 1) rather than a raw event count",
"max_score": 12
},
{
"name": "by() on aggregations",
"description": "Any sum() in alert expressions includes an explicit by() or without() clause",
"max_score": 10
},
{
"name": "Valid YAML alert rule format",
"description": "The file uses valid Prometheus alerting rule YAML structure with 'alert:', 'expr:', and 'for:' keys",
"max_score": 10
}
]
}