BPI Consider Soft State as PROBLEM

[lb2cons]

Hello experts. I'm heavily using Nagios BPI on my server, but a only noticed one little problem with this amazing addon just now.

I'm grouping several checks on a BPI an creating a single check for the BPI group, so, the only notificaiton that Nagios generates is the BPI group (I'm disabling notifications to the services inside the bpi group).

With this new policy I've noticed that problem:

A BPI group considered a service in a soft state as a problem. This is very bad for me because a have services that must be checked up to 10 times before entering in a hard state. With that my BPI check enter hard state before it should as you may see in the example above:

Service still in soft state but it's an essential member:

service_soft_state.png

Because the essential member it's critical, the whole group it's considered as critical(This is correct, but, BPI didn't considered that this service wasn't in a hard state):

nagios_bpi_group.png

The bpi service check it's now with CRITICAL state, but we know that this is a false alarm:

bpi_check.png

How about that? Is it possible to configure BPI to consider only hard state?

[ssax]

What version of XI are you using? You can grab it from the bottom left hand side of the web interface.

Also, go to Admin > Manage Components and find the Nagios BPI component and tell me what version you have so that I can take a look at the code.

Thank you!

[lmiltchev]

I was able to recreate the issue and filed an internal bug report (TASK ID 6452).

example01.PNG

example02.PNG

[lb2cons]

Hello lmitchev!

Thanks for your update, how can I track this task?

About the version:

Nagios XI: 2.5
Nagios BPI Component: 2.3.3

[ssax]

That is an internal task, unfortunately there is no way for you to track its progress. I couldn't find an easy fix for this, the developers will need to do it.

Thank you

[lb2cons]

Any news?

[lmiltchev]

I can see that several of the BPI bugs have been fixed already by our devs, but this one hasn't been worked on yet. I don't have an ETA on it, but once the bug has been filed internally to our system, it will get fixed as soon as our developers have time to get to it.

[lb2cons]

Any update about this issue?

[hsmith]

What version are you currently on? There have been a lot of updates since this post.

[lb2cons]

Nagios 5R1.0