Practise the standard verbs for configuring Grafana dashboard alerting.
0 / 5 completed
1 / 5
Fill in: 'We ___ an alert rule directly on the dashboard panel so a threshold breach fires a page without a separate, easily forgotten config file.'
We 'define an alert rule' — the standard, established Grafana collocation for declaring a threshold-based alert. The other options aren't the recognised term here.
2 / 5
Fill in: 'Building a dashboard without any alert rules can ___ a metric quietly crossing a dangerous threshold overnight with nobody watching.'
We say no alerting will 'leave' a breach unnoticed — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a noisy alert temporarily during planned maintenance so on-call isn't paged for a change we already know is happening.'
We 'silence an alert' — the standard, established collocation for suppressing notifications during expected activity. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a critical alert to the on-call pager and a lower-severity one only to a Slack channel, so paging matches actual urgency.'
We 'route an alert' — the standard, established collocation for directing a notification to the right channel by severity. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ fired alerts weekly to prune the ones that never led to real action, so alert fatigue doesn't dull the response to a genuine incident.'
We 'review' alerts — the standard, simple collocation for periodically reassessing whether a rule still earns its page. The other options are less idiomatic here.