Delay host and service notifications for newly added hosts

3 votes

we use scaling plans for non persistent terminal servers, which means servers are turned on or off based on the workload, and we can't set static downtimes for these systems.

dynamic adding and deleting hosts works fine so far (implemented with the "Periodic service discovery" and "Automatic host removal" settings) but it takes a few minutes until the hosts checks are not critical.

That is why we still need to find a variable solution for the out of business and emergency call times in terms of the notification delay.

I think that this would be the best solution for us and maybe also for other customers.

Under consideration Notifications Suggested by: NicolaD (21 Sep, '23) • Upvoted: 13 Oct, '23 • Comments: 3

Comments: 3

25 Sep, '23
Martin Hirschvogel Admin
I adapted the title, so that it becomes a bit clearer. Does it reflect your suggestion?
26 Sep, '23
Nicola
Hi Martin,

thanks for your suggestion which correctly addresses the main issue, as well we may need the notification delay for certain time periods (which is currently not possible to configure), because during the day citrical checks are handled quickly and should also be alerted quickly, however at night we only want alarms that have status critical for more than 30min.

Thanks
Nicola
02 Oct, '23
Martin Hirschvogel
The time period feature already is part of the notification rules. Thus you could re-use that.
But we would still need a new logic which handles a) newly added hosts) and b) is conditional based on host/service state