Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #2919] allow disabling notifications with expire time #1051
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2919
Created by mfriedrich on 2012-07-30 19:57:32 +00:00
same as acks with expire time, but just for notifications. though i do believe that with modified_attributes within #2473 and #2474 those changes will be reflected a bit better, so i am not yet convinced that this should happen on a host or service level, but rather let it happen only globally as i misinterpreted in #905
Updated by mfriedrich on 2012-07-31 08:01:36 +00:00
from the original issue
Updated by pvdputte on 2014-10-27 15:11:48 +00:00
As rbrinkmo mentioned in the original #905 issue, a scheduled downtime is interpreted like a 'planned maintenance' by SLA reporting, which is exactly what we want (e.g. downtime during this timeframe does not count for the maximum allowed downtime for the month).
We use regular 'ack' while investigating an incident, hence this downtime does get counted for the SLA report. Again exactly what we want.
However, if the host/service is continually spamming our sysadmins with 'OK' and 'Critical' messages because it's flapping, they have no other option but to disable notifications manually (and maybe forget to re-enable it), or to add a scheduled downtime (messing up SLA reporting => not an option really). 'flap detection' is something we wish to steer clear of because we might miss actual incidents because Icinga stops sending out alerts and people might not have woken up in time.
The only option we have is to bolt on some in-house tool to disable and re-enable notifications on a service or host for us. Or is there an clean alternative?