During maintenance on db1181 "profile::monitoring::notifications_enabled: false" was set, but it still paged. Similar report by @RKemper on IRC from last night:
<ryankemper> Anyone been having trouble downtiming hosts in Icinga? For example I just tried manually downtiming `elastic2059` and never saw it actually take effect in Icinga <ryankemper> Feels like Icinga is getting the request fine but then failing to actually process it in the backend <ryankemper> ^ Following up I now see those downtimes in place so it does seem like the icinga backend is just really backlogged
Followups
- (critical) Alert on "max check latency" shooting up
- Depending on how frequently the above fires, consider auto-remediation (i.e. an Icinga restart)