Practise the standard verbs for tuning Datadog monitors to reduce noise.
0 / 5 completed
1 / 5
Fill in: 'We ___ the alert threshold against several weeks of historical data so a monitor fires on a genuine anomaly instead of routine, expected daily variation.'
We 'tune a threshold' — the standard, simple collocation for adjusting a monitor's trigger point based on real data. The other options are less idiomatic here.
2 / 5
Fill in: 'Setting an alert threshold without checking historical data can ___ the same monitor firing every single night during a completely normal traffic dip.'
We say an untuned threshold will 'leave' a monitor firing on normal variation — the standard, natural collocation for the resulting noise. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a noisy monitor temporarily during a planned maintenance window, so on-call isn't paged for a change that's already known and expected.'
We 'mute a monitor' — the standard, established Datadog collocation for suppressing notifications during known activity. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ every monitor with the service and team it belongs to, so a page during an incident routes straight to the people who actually own that system.'
We 'tag a monitor' — the standard, established collocation for attaching ownership metadata used for routing and filtering. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ every firing monitor monthly to prune the ones that never led to real action, so alert fatigue doesn't dull the response to a genuine incident.'
We 'review' monitors — the standard, simple collocation for periodically reassessing whether an alert still earns its page. The other options are less idiomatic here.