I thought about the way having local ido2db instances on every icinga host
being more robust against outages of single components. I haven’t tested a
setup with single ido2db instance but I would say that both approaches are
possible. The key aspect is setting a unique instance name in idomod.cf
Hmm...I don't use multiple ido2db processes. I have one ido2db process
running on the "collector" host running the database. Then on my icinga
instances, I have an idomod.cfg where instance_name is set to be unique,
and they use a tcpsocket connection to the ido2db process on the
collector host
Hi Marco,
so if I get this correct, icinga-web is configured with a *single*
database connection and all your IDO2DB instanced write to this very
same database but each with a different instance name so they can be
told apart? If this is the way it works, it seems like an awesome
solution. I conne
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
