Customizable Min-Operator

[sjulez]

Is your feature request related to a problem? Please describe.

My Business Process containes Subprocesses with > 10 Nodes. Our Definition is that alarming should start when at least 2 Nodes (Hosts) are down. Currently I have to brake down all Processes into groups not bigger than 10 Servers to be able to do proper alarming based on the module.

Describe the solution you'd like

When I chose the MIN-Operator, I want to be able to define a Value.

Describe alternatives you've considered

Additional context

[willfurnell]

This sounds like a great feature request! I'd also be interested in it :)

[MarcusCaepio]

+1 !!!
I just started to use BP and need definitely a possibility to check more than 9 nodes. Why not just create a variable field X for min, wer one can define it free instead of choosing from dropdown?
@nilmerg as a real dirty workaround, would it work to change a 9 to e.g. 15 in the config ini?

[nilmerg]

Probably, though don't expect to be able to edit this process in any way in the UI from there on.

[lippserd]

I think we should introduce a new operator for that.

[lippserd]

Would #278 help here?

[lippserd]

We could also introduce something like worst n of: a + b +c which selects the worst of the worst n child node states.

[robinwolny]

@lippserd would be possible to have a percentage? Like MIN 50% of nodes must be OK.

[slalomsk8er]

@lippserd would be possible to have a percentage? Like MIN 50% of nodes must be OK.

How about something more flexible like giving nodes adjustable weights and weight thresholds?

Sum of child node weights results in:

0 to X = Critical
X to Y = Warning
Y to ∞ = OK

As the operators are limited in the config syntax, it would need to happen as comments I guess or it would break some backwards compatibility.

[wp-perc]

• 1

The actual number of MIN is quite limiting, so I am also strongly interested in it.