Hello XI support
How to prevent BPI group condition triggering CRITICAL when:
percentage Health are actually all WARNINGS (but the GROUP is critical)
essential member is in WARNING (but the group is CRITICAL)
essential member is UNKNOWN (but the group is CRITICAL)
This does not seem right and prevents "smart" usage of BPI groups for ticketing
BPI group critical when essential is WARN or UNKNOWN
Re: BPI group critical when essential is WARN or UNKNOWN
BPI weighs the WARNING and CRITICAL states the same so there's not a setting to change the behavior for your first point, but your second and third points are configurable. See the attached screenshot.
I will file a feature request to allow the adjusting of weight for different states.
I will file a feature request to allow the adjusting of weight for different states.
You do not have the required permissions to view the files attached to this post.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: BPI group critical when essential is WARN or UNKNOWN
Thank you.cdienger wrote:BPI weighs the WARNING and CRITICAL states the same so there's not a setting to change the behavior for your first point, but your second and third points are configurable. See the attached screenshot.
I will file a feature request to allow the adjusting of weight for different states.
Please close the thread (and file that feature request
