New statuses

thomasschmeidl · Post by **thomasschmeidl** » Sat Dec 09, 2006 9:07 am

First of all thanx a lot for the new statuses "normal" and "warning" which are very helpful for us and propably many other admins, too!!!

In our first tries we realized that a test will have the status "normal", if both expressions (for warning and normal) are true.

Can I expect this behaviour for all tests?

Regards

Thomas

KS-Soft · Post by **KS-Soft** » Sat Dec 09, 2006 12:12 pm

You are welcome

In our first tries we realized that a test will have the status "normal", if both expressions (for warning and normal) are true.
Can I expect this behaviour for all tests?

Correct

Regards
Alex

JuergenF · Post by **JuergenF** » Thu Dec 28, 2006 6:30 am

KS-Soft wrote:You are welcome

In our first tries we realized that a test will have the status "normal", if both expressions (for warning and normal) are true.
Can I expect this behaviour for all tests?
Correct

Regards
Alex

Doesn't it make more sense, to change that behaviour ?
Warning is more serious and if a warning expression is true it should overrule the status to be warning instead of normal.

KS-Soft · Post by **KS-Soft** » Thu Dec 28, 2006 11:18 am

Normally you should use different expressions and only one should return True

Regards
Alex

JuergenF · Post by **JuergenF** » Thu Dec 28, 2006 11:53 am

KS-Soft wrote:Normally you should use different expressions and only one should return True

Regards
Alex

Not in case of escalation - what is my idea of the new statuses.
OK - Normal - Warning - Bad.

And of course you can build expressions that are unique - but that are more complex.

CPU test with 75 %
enable “Treat Warning status as Bad” option
enable “Use Warning" status” option and provide ("%SuggestedSimpleStatus%"=="DOWN") and (%FailureIteration% < 10)
enable “Use Normal status” option and use expression like ("%SuggestedSimpleStatus%"=="DOWN") and (((%FailureIteration% < 5) and ("%Reply%" <= "90 %")) or ((%FailureIteration% <= 2) and ("%Reply%" > "90 %")))

In most cases both expressions are TRUE and the more specific "Normal" overrules the "Warning". And the warning expression can be kept very simple.

So it's OK to allow overlapping expressions and define a priority, from my pov.
I only think it's more logical to give the priority to the "Warning" expression.

But it's a change of program behaviour - so it has to be decided before the final release. That's why I'm talking about that.
But of course it's your decision.
And don't worry, I'll keep using HostMonitor in any case

Regards

Juergen