Hello, I would like to propose an enhancement (feature request) to the Nagios XI Business Process Intelligence (BPI) module that would significantly improve its functionality and usability in complex monitoring environments.
In the current implementation of Nagios XI, when a child service within a BPI object transitions to a non-OK state (warning, critical, or unknown), the parent object appropriately inherits this state, reflecting the issue in the overall health of the BPI tree. However, when the issue on the child service is acknowledged, the parent object does not adjust its inherited state accordingly. This results in the parent object continuing to reflect a critical state despite the acknowledgment of the underlying issue.
We want the state inheritance mechanism in BPI objects to be enhanced and account for acknowledgments on child services. Specifically, when a child service issue is acknowledged, the status of the parent object should become OK (or adjust its state appropriately to reflect this acknowledgment), provided there are no other unacknowledged issues affecting its status.
Regards,
Enhancement of BPI Object State Inheritance
Re: Enhancement of BPI Object State Inheritance
That sounds like a really practical and useful enhancement for Nagios XI's BPI module. It would definitely improve the overall monitoring experience in complex environments. The ability for parent objects to adjust their state based on acknowledgments of child services seems like a logical and valuable addition. It would ensure that the overall health status accurately reflects the current state of all monitored services.
Re: Enhancement of BPI Object State Inheritance
Hi @coitop,
I went ahead and filed an issue in our internal tracking, and we'll be looking into this enhancement request going forward. Thanks for your input!
I went ahead and filed an issue in our internal tracking, and we'll be looking into this enhancement request going forward. Thanks for your input!
Re: Enhancement of BPI Object State Inheritance
Hey @coitop
Unfortunately there isnt since its in our internal system used for tracking issues/features. We are unable to give a time frame on when this might get addressed however if you want to keep an eye out for it you can take a look at our change log here on new releases.