Practise the standard verbs for writing reliable Prometheus alert rules.
0 / 5 completed
1 / 5
Fill in: 'We ___ an alert rule on a metric that actually reflects user-facing pain, not just internal noise.'
We 'write a rule' — the standard, simple collocation for authoring an alerting expression. The other options are less idiomatic here.
2 / 5
Fill in: 'A threshold set too tight can ___ the on-call engineer with pages for perfectly normal fluctuations.'
We say a tight threshold will 'flood' on-call with alerts — the standard, natural collocation for overwhelming noise. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a "for" duration on flaky alerts so a brief blip doesn't page anyone before it resolves itself.'
We 'attach a duration' — the standard collocation for tying a condition to a rule so it only fires once sustained. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ every alert rule against historical data before shipping it, to catch an unrealistic threshold early.'
We 'test a rule' — the standard, simple collocation for validating it before relying on it in production. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a runbook link inside every alert so whoever gets paged knows exactly where to start.'
We 'include' a link — the standard, simple collocation for adding useful context to an alert. The other options are less idiomatic here.