Nagios BPI groups

[atsb]

Hello!

About nagios XI environment
1) Linux Distribution and version? Centos7
2) 32 or 64bit? 64bit
3) VMware Image or Manual Install of XI? Manual install
4) Are there special configurations on your system, ie; is Gnome installed? Are you using a proxy? Are you using SSL? SSL
5) NagiosXI version: 5.5.5

I am facing weird issue in BPI where top level group does not go to "Critical" state and stays "OK". This happens when the same group has one sub group added twice. I will provide example with pictures:
This way it works:

nagios_bug3.png

This is when it breaks:

nagios_bug4.png

Now i am not sure if this is a bug or its not even intended to be used like this. Could you please explain it ?

[ssax]

I labbed this up and I was unable to replicate it.

Please PM me this file:

Code: Select all

/usr/local/nagiosxi/etc/components/bpi.conf

Thank you

[atsb]

I sent you BPI.conf via message. Interesting thing to keep in mind is that when "TEST-1" and "TEST-2" are both in critical status then top level group will also go in critical status but when there is only one of them critical then top level group stays OK.

nagios_bug5.png

[ssax]

I am able to replicate this on mine, I've reached out to get clarification from the developers. My initial reaction is that it's a bug and it should be showing critical but I need to make sure so I don't give you wrong information.

[atsb]

Any news about this ?

[ssax]

We need some more time to figure this out, we are unable to replicate it when we set it up the same manually but we can replicate it if we import your config. It looks like a bug or a misconfiguration issue but I'll need to get you an answer tomorrow after I can dig into it more.

Thank you

[atsb]

Once again, any ideas ? if its not intended to be used like this then i can find a workaround for this but it makes things little more confused.

[ssax]

I do see that if you remove the RANDOM group it does work as expected as you noted. I wonder if it's excluding it because it's already counted under the other one. Looking at the code now.

[ssax]

So, If I duplicate the RANDOM group and change it to RANDOM2 and then edit the top Backend group and use the RANDOM2 in there instead of RANDOM it works properly, as a workaround can you do this and let me know if that fixes it for you?

[atsb]

Yes, creating new group with same members then it works.