HostGroup Mapping issue !!!

[rajsshah]

Hi Team
Lets say I have a Hostgroup HG_LInux and I have few linux servers servers A, B , C etc .. I go to Host group HG_Linux and add all the host as its member .
Now when I go to Individual host config ( lets say A ) I still see 0 under Hostgroup . When I click on hostgroup I can see that HG_Linux group is having a chain icon ( Relationship defined elsewhere) . This happens if do the other way around as well .Why is this weird behavior??

No matter from where I add / create the mapping it should be visible from wither side . It should not give the count as 0 in the config . This makes sysadmin confuse . Is there any reason why this has been implemented this way ??

[benjaminsmith]

Hi,

Nagios XI is uses Nagios Core to handle monitoring, scheduling and alerting, and core uses configuration files. The Core Configuration Manager, is a graphical interface for editing these configuration files.

When you see the chain icon (Relationship defined elsewhere), it's informing the user that this setting relationship is defined in another configuration file. However, result is the same.

If you go to CCM > Monitoring > Host Groups > Manage Hosts, the hosts will show up in the Assigned column on the right. Now If you go to CCM > Monitoring > Hosts >... click on the host and select Manage Hosts Groups you see the relationship icon for the hostgroups. However, if you define the hostgroup membership in the host object definition itself, the Assigned list on the right will show the hostgroup. In short, it depends where the association is defined. You can define hostgroup membership in either a hostgroup configuration definition or the host definition itself, and this behavior is reflecting that.

You can view the configuration file from the CCM by clicking on the configure icon (see image).

Let me know if that answers your question.

[rajsshah]

Hi
do you guys have any use cases / whitepaper for managing the servers and their services via use of HOSTGROUP, SERVICE GROUP and CONTACT group .
I have different env ( prod/acc) with different services with different AMS team . I want to make use of HOSTGROUP and service group , but need some example .

[benjaminsmith]

Hello,

do you guys have any use cases / whitepaper for managing the servers and their services via use of HOSTGROUP, SERVICE GROUP and CONTACT group .

Groups are simply a way of organizing hosts, services or contacts into logical categories. When you say 'managing', what specifically would you like to do with groups?

[rajsshah]

Consider below scenario
I have 50 Linux servers and I want to monitor the CPU utilization on all 50 servers .
If CPU utilization goes beyond 80% I want to send alert to SYSADMIN ( SYSADMIN_Contact_Group)

I can create a HOST group : LINUX_HG and assign all 50 servers to this hostgroup.
I can then create CPU_Service check --> Assign Monitoring conact as ( SYSADMIN_Contact_Group) and map Host group as LINUX_HG

This means my CPU check service run on all 50 hosts and will send alert to SYSADMIN_Contact_Group if any thing goes wrong . Am I correct till this point ??? I think yes

Now , AMS team ( AMS_CONTACT_GROUP ) also want CPU check alert but only for 5 servers ( out of that 50 ) that are part of that same HG .

- If I simply add their CONTACT group under the CPU_Service service , then apart from getting alert for those 5 servers the will get alert for other 45 servers as well .

- If I create new service for AMS team , then there are 2 separate checks that will run on those 5 servers ( 1 for sysadmin , 1 for AMS )

- If I negate ( !) those 5 servers under SYSADMIN CPU check then I Will have to add their group under AMS CPU check service .

This is just one scenario , there are many others .. and mostly we have automated registering for HOST and services via ansible .

[benjaminsmith]

Hello @rajsshah,

This means my CPU check service run on all 50 hosts and will send alert to SYSADMIN_Contact_Group if any thing goes wrong . Am I correct till this point ??? I think yes

This is correct, but you can define different Alert Settings for every CPU service under each host. For example, change the Alert settings for the 5 servers in the AWS team. The bulk modifications tool is useful for modifying multiple hosts or services at the same time.

Alternatively, you could experiment with service escalations as you can adjust how and to who notifications are sent to. Keep in mind that escalations take priority over existing notification options.

Understanding Notification Escalations