Nagios configuration generation

This is handled by nagconfgen.

Contact groups are created with the name of

• hostgroupX_servicegroupY
• keywordX

The hostgroupX_servicegroupY is the hostgroup and servicegroup intersection. Hosts and services are put into the appropriate contactgroup. The appropriate hosts are also in the contact groups.

The keywordX contact group contains all services in that keyword as well as the hosts they are on.

Contacts are then assigned to the appropriate contact groups via the notification profiles (for notifications) or the. This then defines the flow of notifications from hosts or services to contacts.

Notifications are defined to come from either the active monitoring server or the master.

However, the master needs to know the difference between a host/service defined on a slave and something it is actively monitoring itself, because the notification methods to use are then different.

This is solved by using opsview_distributed_notifications. This broker module works out whether to block the notification from occurring. A contact group is used, called ov_monitored_by_master, which defines the objects monitored by the master server.

This has removed all the masterprofiles and distprofiles definitions that used to litter the configuration.