Here are some important points to consider about the logic behind how APM deals with associations between Hosts, Services, and Host groups.
1. Associating a host with a host group is done in the “Host” definition entry under the “Host groups” field.
2. Association of a service with a host is done in the “Service” definition entry under the “Hosts” field. This is done automatically (for host and service) when you use the auto detection engine of BLESK to export devices into the APM module.
3. Another important point is how the auto detection of BLESK deals with contacts that should be associated with a host or service. By default, only one contact (admin) is created and this contact is a member of all available contact groups.
Note: All pre-defined contact groups relate to their corresponding host groups are associated with them by the auto detection engine during exportation of devices to be monitored by BLESK.
4. Services associated with a host, have their contacts already defined in their configuration file template according to the type of service. For example, by default a WMI service template will have the “windows- admins” contact group. The same applies for all the other different service templates.
5. Finally, pre-defined host groups are available and are used by the detection engine to classify devices according to their type. This association is then automatically linked in the “Host groups” field of the “Host” definition file for each host.
We don’t use the Host groups definition entries located under the “Supervision” left panel of the Administration section of APM to manage hosts with groups.
6. You may still use it if you wish, or use it in combination with our default approach which consists of using the “Host” definition entries located under the “Supervision” left panel of the Administration section.
