Status roll-up doesn't work for component?

Hi. I have an application with only one component (windows powershell monitor).
This component have 2 outputs:
1. Critical is not equal to 1
2. Critical is not equal to 0
Status Roll-up of the component is show best status

But if one of outputs became critical, my component is also became critical. Why? Status roll-up doesn't work?
You can see here, what only first output is Critical, and the second is okay.

Find more posts tagged with

rollup

Accepted answers

All comments

christopher.t.jones123

@omavel do you have an exit code in the script defining status?

omavel

Nope, but I have thresholds

omavel

Actually I wanna reach this behavior: Application status is Critical ONLY IF ALL it's child are critical.

Because one neighbor loss is not mean replication is not working. But if all neighbor unavailable, it's time to alert. Problem is - different number of neighbors - it can be 1, or 2, or 3, or 4

Now I made a new app with 4 components (for each neighbor). For those nodes where neighbor count is less then 4, I manually disable extra components.

Still don't know how to implement this logic