Hi Florian,
we’re using a similar setup. There are f.e. four Icinga instances with their
own ido2db daemon running. In ido2db.cfg each of them is configured with its
own instance name. This results in the status data getting written in context
of the instance, preventing collisions. These four
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey everybody,
since for my last problem (see
https://lists.icinga.org/pipermail/icinga-users/2014-February/007931.html)
it seems no one knows a solution, I am going to try a different approach.
The scenario is as before: I have two distinct servers
Hi Florian,
we’re using a similar setup. There are f.e. four Icinga instances with their
own ido2db daemon running. In ido2db.cfg each of them is configured with its
own instance name. This results in the status data getting written in context
of the instance, preventing collisions. These four
Hey everybody,
since for my last problem (see
https://lists.icinga.org/pipermail/icinga-users/2014-February/007931.html)
it seems no one knows a solution, I am going to try a different approach.
The scenario is as before: I have two distinct servers running icinga
and I want to monitor them in o
