Recently I was asked why alerting in a NetEye 4 environment isn’t run via the central master, but instead via the satellites. The background to this is that the NetEye Master is located in Italy, which controls various satellites in other European and African countries.
It’s therefore a strategic decision that alarms are sent from the local satellites for reasons such as SMS costs, interruptions in WAN connections, etc.
To achieve this, I made the following settings.
icinga2 feature enable notification
See this example:
If you inherit settings from other “notification templates”, these must also be in exactly the same zone. Otherwise the configuration will not work on the satellite because the satellite does not recognize this notification template.
Next I create a “user template” for this zone, which under “Zone settings” again refers to the desired zone. This is necessary because the user on which the notifications are based is created precisely in this zone by assigning this template. Otherwise the zone does not recognize the user, the Icinga configuration is not adopted, and thus the Icinga service on the satellite stops.
Then I create a user with email alerting who should be the one notified for this zone. It’s important that I use the “notify-all-events-rome” template that I just created above so that this user is created on the desired satellite.
Here’s an example again:
Finally, of course, you have to create the “notification apply rules” that apply to this user and zone. It’s important to note that it uses the notification template and the user we just created. Of course, the assignment rule must be selected for the desired objects.
The final example:
Finally, for this configuration I’d like to underline a few essential topics that are very important for correct functionality:
I’ve configured this setup even on a seven satellite environment, where I’ve received email and SMS alerts, some of which are attached to the satellite servers via various gateways.