Using options like --details or --root-cause, when using icingacli to do the monitoring check, doesn't always give the output needed when a BP is based on an XOR or NOT condition (possibly others). It shows the problem states, but with those Operators the problem with the BP could be related to the absence of a problem in the node's members.
Describe the solution you'd like
A simple "--full-tree" option would allow info. for the entire BP to be included. A more advanced solution would be to know when to include non-problem states based on the Logic operator used. (example: a problem for "service1 xor service2" would include the service states for both services if they are both ok, or both critical.)
Describe alternatives you've considered
I personally prefer to avoid these types of BPs because problems are not supposed to exist (by definition). But I have situations in where this is how someone wants to monitor active-passive systems and, technically, "root cause" should show what caused the logic to trip on these business process checks.
Using options like --details or --root-cause, when using icingacli to do the monitoring check, doesn't always give the output needed when a BP is based on an XOR or NOT condition (possibly others). It shows the problem states, but with those Operators the problem with the BP could be related to the absence of a problem in the node's members.
Describe the solution you'd like
A simple "--full-tree" option would allow info. for the entire BP to be included. A more advanced solution would be to know when to include non-problem states based on the Logic operator used. (example: a problem for "service1 xor service2" would include the service states for both services if they are both ok, or both critical.)
Describe alternatives you've considered
I personally prefer to avoid these types of BPs because problems are not supposed to exist (by definition). But I have situations in where this is how someone wants to monitor active-passive systems and, technically, "root cause" should show what caused the logic to trip on these business process checks.