Page 1 of 1

BPI Check - List all Problems

Posted: Fri Apr 03, 2015 5:12 pm
by lb2cons
Hi everyone, I'm looking for some automation on check_bpi to list all problems of a given group.

Check_bpi currently shows this result when health it's below te threshold:

WARNING - Group health is 90.91% with 2 problem(s) | Health=90.91%

If a Essential member is critical/warning then check_bpi shows what member it's critical/warning, like:

CRITICAL - Essential member "CSD-SRV_SQL_03 : Drive E: Disk Usage" is in a problem state! Group health is: 64.52%. | Health=64.52%

I wanna modify the result and show all members that are in a problem state (Only when health it's below the threshold).

Like this :

WARNING - Group health is 90.91% with 2 problem(s) - "CSD-SRV_SQL_03 : CPU Usage", "CSD-SRV_SQL_04 : Load Average" | Health=90.91%

This will help me to make a quick diagnostic of a group when essential members are ok but several members aren't.

Can someone give me a hint?

Re: BPI Check - List all Problems

Posted: Mon Apr 06, 2015 12:14 pm
by tmcdonald
This is something that might be best entered in as a feature request. For any development work beyond a few simple modifications we need to get the dev team involved. This usually means either a bug/feature report, or custom development if it is something that needs to be done on a timeline. I can file this as a feature request but I can't guarantee when/if it would be added in. Custom development would have a guarantee but you would need to talk to Sales about that.

Re: BPI Check - List all Problems

Posted: Sat Apr 11, 2015 11:59 pm
by lb2cons
I understood your concern.

I'm interested in implement this by myself if possible, but I want some tips on how to do this. Can you help?

Re: BPI Check - List all Problems

Posted: Mon Apr 13, 2015 9:09 am
by tmcdonald
That's a pretty significant change to the logic. Not being a true developer myself and only having peeked into the BPI source once, I can't really provide much useful insight. If you have specific development questions we may be able to answer them, but again this change is not likely to be a simple 2-line fix.