Feature Request: Expand Event Rule Filter Options by Zone

[HactarofDoom]

Within the Event Rule context the filters for hostgroup and servicegroup offer a good starting point for initial filtering, however additional filters for zone or in the long run custom fields (like location) would immensly increase flexibility and handling team allocation per zone / location without needing the extra "bloat" of added groups to handle the same functionality.

As an example with all host containing a geolocation field (like ours do) and all hosts within that location beeing in a seperate zone a filter for either zone or the geolocation field would replace the hostgroup/<location> and servicegroup/<location> at the minimum.

This would help even more if the hostgroups / servicegroups within the zone need further granulation that one would rather handle on a more global level like sorting services / hosts into severity groups depending on how important the service is for the infrastructure. Setting servicegroups for essential / development / testing once globaly and filtering notifications per zone / location is way less overhead than having those same servicegroups per zone / location.

[oxzi]

Thanks for your input! We are currently reworking the event rule filtering logic to allow more source specific filters, such as custom variables or every other available object property for Icinga 2. A prototype is being developed in #324.

[HactarofDoom]

That's awesome! Working further with the module in the last few weeks I saw that in addition beeing able to use Alterts thrown by (for example) the Icinga Business Process Module and the like would be great to increase flexibiliy and control who gets notified about what.

There are more ideas and input I have for the module but that would need do go into seperate topics as they do not relate to Evnet Rules.