Just want to emphasize that I'm a paying customer and it would be great to see this in one of the next releases!
Kind Regards,
Helmut
mikcik wrote:Currently a Nagios BPI group will go to a CRITICAL state if the threshold is met because the services are either WARNING or CRITICAL.
I think it would make a lot of sense to make this customizable to only react to service problems that are CRITICAL.
Meaning that WARNING levels of services are ignored and won't result in the Nagios BPI to go CRITICAL.
In many cases a WARNING level means a degradation of the service but not necessarily an unavailability, which we try to model with the Nagios BPI groups.
Unfortunately the part of the source code where this logic resides is obfuscated in Nagios XI, otherwise I would have provided a patch myself.
I think the implementation would be straight forward and would only require one parameter in the config.
If I post this feature request internally it will not appear on the public tracker, however internal feature requests tend to be looked at more frequently. Is that alright?
Also, just for your information, the Nagios Ideas forum is not very high-traffic and is more used for "what-if" than formal feature requests. If you have ideas in the future, feel free to just post them in the Nagios XI subforum.
I posted an internal feature request (TASK ID 5131) to our system. There is no guarantee if/when this functionality would be implemented. Bug reports take precedence over feature requests. Anyway, I will be locking this topic.
Be sure to check out our Knowledgebase for helpful articles and solutions!