Associate two tests
Associate two tests
This is a feature i would very much like to see in HM.
I have configured two seperate tests for the end points of a tcp/ip connection. Can i create a third test that will go red when either of the above two tests goes red and then go back to green once both of the above two tests are green?
I have configured two seperate tests for the end points of a tcp/ip connection. Can i create a third test that will go red when either of the above two tests goes red and then go back to green once both of the above two tests are green?
I think you should use 'and' instead of 'or'...go back to green once both of the above two tests are green
...
('%::TestA::SimpleStatus%'=='UP') or ('%::TestB::SimpleStatus%'=='UP')
Rightwhere TestA is the test name, right?
Quote from the manul:The keyword UP should be replaced by the value in the test response, like 1 or 2 or Ok, or is it a standard keyword?
%SimpleStatus% - This macro can have one of the three text values:
- "UP" for all good statuses (Host is Alive, Ok);
- "DOWN" for all bad statuses (No answer, Bad, Bad Contents);
- "UNKNOWN" if status of the test is Unknown or Not Resolved.
Please read the manual.
Regards
Alex
I have configured these 3 tests
a ping test to 10.1.1.1-test a
a ping test to 10.2.1.1-test b
and a ping test to 10.1.1.13-test c
What i would like to do is to trigger test c if either of the a and b tests have %SimpleStatus% NOT UP
Is this the proper expression to use?
('%::test 10.1.1.1::SimpleStatus%'<>"UP") or ('%test 10.2.1.1::SimpleStatus%'<>"UP")
Cause it is not working

a ping test to 10.1.1.1-test a
a ping test to 10.2.1.1-test b
and a ping test to 10.1.1.13-test c
What i would like to do is to trigger test c if either of the a and b tests have %SimpleStatus% NOT UP
Is this the proper expression to use?
('%::test 10.1.1.1::SimpleStatus%'<>"UP") or ('%test 10.2.1.1::SimpleStatus%'<>"UP")
Cause it is not working

By the way, i don't think this post any longer qualifies for the wish list category; ------- Test #1 -------
Method = Ping
;--- Common properties ---
Title = test 10.1.1.1
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 60
Alerts = Do nothing
ReverseAlert= No
UnknownIsBad= Yes
UseCommonLog= No
PrivLogMode = Default
CommLogMode = Default
;--- Test specific properties ---
Host = 10.1.1.1
Timeout = 2000
Retries = 4
MaxLostRatio= 100
DisplayMode = time
; ------- Test #2 -------
Method = Ping
;--- Common properties ---
Title = test 10.2.1.1
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 60
Alerts = Do nothing
ReverseAlert= No
UnknownIsBad= Yes
UseCommonLog= No
PrivLogMode = Default
CommLogMode = Default
;--- Test specific properties ---
Host = 10.2.1.1
Timeout = 2000
Retries = 4
MaxLostRatio= 100
DisplayMode = time
; ------- Test #3 -------
Method = Ping
;--- Common properties ---
Title = test
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 60
Alerts = Do nothing
ReverseAlert= No
UnknownIsBad= Yes
UseCommonLog= No
PrivLogMode = Default
CommLogMode = Default
SyncCounters= Yes
SyncAlerts = No
DependsOn = expression
DpExpression= ('%::test 10.1.1.1::SimpleStatus%'<>"UP") or ('%test 10.2.1.1::SimpleStatus%'<>"UP")
DpOStatus = 'Host is alive'
;--- Test specific properties ---
Host = 10.1.1.13
Timeout = 2000
Retries = 4
MaxLostRatio= 100
DisplayMode = time

Hi Alex,
Thanks for the tip. I corrected the expression but i am getting Waiting For Master status of the 3rd test while the other two have an UP status, although i have set the 'Host is alive' in the otherwise status field. Is this what i should be getting?
Thanks for the tip. I corrected the expression but i am getting Waiting For Master status of the 3rd test while the other two have an UP status, although i have set the 'Host is alive' in the otherwise status field. Is this what i should be getting?
; ------- Test #1 -------
Method = Ping
;--- Common properties ---
Title = test 10.1.1.1
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 60
Alerts = Do nothing
ReverseAlert= No
UnknownIsBad= Yes
UseCommonLog= No
PrivLogMode = Default
CommLogMode = Default
;--- Test specific properties ---
Host = 10.1.1.1
Timeout = 2000
Retries = 4
MaxLostRatio= 100
DisplayMode = time
; ------- Test #2 -------
Method = Ping
;--- Common properties ---
Title = test 10.2.1.1
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 60
Alerts = Do nothing
ReverseAlert= No
UnknownIsBad= Yes
UseCommonLog= No
PrivLogMode = Default
CommLogMode = Default
;--- Test specific properties ---
Host = 10.2.1.1
Timeout = 2000
Retries = 4
MaxLostRatio= 100
DisplayMode = time
; ------- Test #3 -------
Method = Ping
;--- Common properties ---
Title = test
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 60
Alerts = Do nothing
ReverseAlert= No
UnknownIsBad= Yes
UseCommonLog= No
PrivLogMode = Default
CommLogMode = Default
SyncCounters= Yes
SyncAlerts = No
DependsOn = expression
DpExpression= ('%::test 10.1.1.1::SimpleStatus%'<>"UP") or ('%::test 10.2.1.1::SimpleStatus%'<>"UP")
DpOStatus = 'Host is alive'
;--- Test specific properties ---
Host = 10.1.1.13
Timeout = 2000
Retries = 4
MaxLostRatio= 100
DisplayMode = time