Nagios Support Forum

Hi,
we are currently migrating from TIVOLI monitoring to NAGIOS XI.
The main deployment method used is based on hostgroup inheritance e.g.

SERVICE = CpuUsageWindows
xxxxxHostgroup= Windows_server
xxxxxxxxxxhost1
xxxxxxxxxxhost2
xxxxxxxxxx...

In the future, we plan to use a NAGVIS dashboard and use a ServiceGroups-based app breakdown e.g.

SERVICEGROUP = Application TEST

Having deployed the controls on hostgroups through inheritance we cannot populate the ServiceGroups with checks for individual hosts.

Solution:
To overcome this problem, we intended to (where necessary) deploy the same control as well as on the hostgroup even on a single host.

In this way we are assured of a centralized management of controls through groups, and that control on a single host can be added to the servicegroup of the affected application.

We currently have around 1000 hosts, on each host there are at least 10 controls.

On 500 hosts we should use the solution just described.
We are sure that the control is not duplicated, but could there be any other problems? (Performance, DB data incoherence ...)

One way around that would be for you to define the servicegroups manually in config file in /usr/local/nagios/etc/static and it should allow you to specify the individual hosts (by typing them out), I just tested on my system and this works. You wouldn't see them in the XI CCM though, you would everywhere else, and since Nagvis uses NDO, it should work too.

See here:
Edit: I'm not sure if doing it your way would have any impact on the XI reports given it's technically a duplication of the service if I'm reading what you're posting properly.

Thanks for the answer but it is not clear to me if we can use this method or not.

Thanks for the support

A lot of this really depends on the hardware, it should work fine your way but you will need to monitor for any anomalies if things start slowing down dramatically.