is there a way how to avoid sending notifications on hosts and their services in the first hour these objects are created?
We use custom script which calls Icinga API to create host objects. The services are assign based on host vars.
We create and object and then we create a downtime on the host and all services. Unfortunately users sometimes receive notification about the problem, even that the downtime is set.
We have two Icinga2 masters in a cluster and few satellites. Only Icinga2 master instances are allowed to send notifications.
The weird thing we can’t see all retries in the histroy. And the notification was sent few seconds after first occurency of the error. See attached picture.
What we would prefer, would be to automatically disable notifications for the host and all its services íf the host exists less than 1 hour. Is it possible?
The check on the picture is active check. We use also passive checks.
icinga2 - The Icinga 2 network monitoring daemon (version: 2.13.2-1)
Platform: CentOS Stream
Platform version: 8
Kernel version: 5.18.6-2.gdc.el8.x86_64
Compiler: GNU 8.4.1
Build host: runner-hh8q3bz2-project-322-concurrent-0
OpenSSL version: OpenSSL 1.1.1k FIPS 25 Mar 2021
Disabled features: compatlog debuglog elasticsearch gelf graphite icingadb influxdb influxdb2 livestatus opentsdb perfdata statusdata syslog
Enabled features: api checker command ido-mysql mainlog notification