hi community,
recurring question about rule: “delay <service|host> notifications” w.r.t. differenciating timeperiods (using 1.6.0p9). the issue has been introduced several times like here (back in 2015) or there (recently in december 2019) - but unfortunately no further instructions seem to be common? in our case, this kind of rule logic would also be appreciated. is there anything in progress - or a show-stopper why this is not just a tiny nice2have option? THX!
The show-stopper is very easy to describe. Delay notifications are bound to the object and cannot changed during the runtime of your core.
But the question from december 2019 can be answered.
Configured are recurring notification for your device something like 5 minutes or longer.
Inside the notification system configure your default rule that it only processes the first notification.
For the system with the delayed notification make a rule to cancel all notifications at night time and create a rule after this cancel message that you want a notification but only if your reach the recurring notification counter of 2, 5 or 10. This depends on your needs.
With the rule based notification you can build very complex rule systems for every need out there.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.