Thanks - though the page you linked to is for Icinga, and (forgot to mention,
but perhaps would be apparent from the syntax below) I am running Icinga2.
You did steer me in the correct direction - will put some time in the lab to
try it out. Thanks!
From: icinga-users [mailto:icinga-users-boun
My solution would be to make a custom host variable for the timeout, and then
make your commands use that variable.
http://docs.icinga.org/latest/en/customobjectvars.html
I've used this successfully for very similar needs.
--
Jamila Ruya Khan
(888) 481-3655 x103
jam...@palantetech.coop
On
Sorry, here the versions and features :
Datacenter node :
~ > icinga2 --version
icinga2 - The Icinga 2 network monitoring daemon (version: r2.3.6-1)
[...]
System information:
Operating system: Linux
Operating system version: 3.2.0-4-amd64
Architecture: x86_64
Distribution: Debian GNU/Lin
Am 13.07.2015 um 11:09 schrieb Cyril Chabarot:
Hi,
I've configured Icinga2 in a distributed mode with one satellite node,
but, when the satellite is disconnected from the master, some events
could occur in a satellite zone.
However, all the events detected during the off-line period are
timestam
Hi,
I've configured Icinga2 in a distributed mode with one satellite node, but,
when the satellite is disconnected from the master, some events could occur
in a satellite zone.
However, all the events detected during the off-line period are
timestamped, in the web interface (both icingaweb2 and i
Hi,
I've configured Icinga2 in a distributed mode.
My main machine is in a datacenter, and will have a lot of satellites.
All of these satellites will be located behind very unstable connections,
implying a lot of flaps.
For now I only have one satellite and I’ve configured it with 3 zones
