Master Testts

Mikevirtu · Post by **Mikevirtu** » Wed May 20, 2015 12:36 am

Hi, Alex!
if I put two master test in the test - they both have to be Alive before you perform this test?
Master Test 1 == Alive && Master Test 2 == Alive -> run This Test
or
Master Test 1 == Alive || Master Test 2 == Alive -> run This Test
I have very big spam now, and I no undestand why?
Regards. Mike.

KS-Soft · Post by **KS-Soft** » Wed May 20, 2015 5:16 am

if I put two master test in the test - they both have to be Alive before you perform this test?

If you are using "this test depends on another test(s)" option, then yes, they both have to be Alive

I have very big spam now

Not sure what exactly this means. Could you please clarify?

There are couple usefull options

Recheck dependant test items when master test status has been changed
This option tells HostMonitor to recheck all dependant test items immediately after their master test failure or recovery (otherwise tests will be executed on regular schedule). This helps to maintain more accurate statistic information.

Consider status of the master test obsolete after N seconds
This parameter is used by the program to determine whether the Master test status is up-to-date. Before starting a dependent test HostMonitor checks the status values of the Master tests defined on it. If Master test was performed more than N seconds ago, HostMonitor will recheck the Master test item before checking dependant items.

Please note: HostMonitor makes an exception for SNMP Trap test methods. If such test is used as Master test, its status never considered as obsolete. In other words status of Master SNMP Trap test will always be considered as up-to-date, regardless of the time when last trap message was received.

Regards
Alex

Mikevirtu · Post by **Mikevirtu** » Wed May 20, 2015 5:59 am

Not sure what exactly this means. Could you please clarify?
example - I have test with Master Test (ping router). This test send me message No Answer Status but Master Test Bad.

Could I use option Recheck dependant test items when master test status has been changed without all tests? I think no. It is global option.

Could I use Consider status of the master test obsolete after N seconds for dedicate tests?

I think I can resolve this situation by many masters test?

KS-Soft · Post by **KS-Soft** » Wed May 20, 2015 6:19 am

example - I have test with Master Test (ping router). This test send me message No Answer Status but Master Test Bad.

May we see logs?
When master test set Bad status? when dependant test set Bad status?
HostMonitor version?

Could I use Consider status of the master test obsolete after N seconds for dedicate tests?

No, but there is "Recheck dependant test items" option for "Repeat test" action
http://www.ks-soft.net/hostmon.eng/mfra ... #actRepeat

I think I can resolve this situation by many masters test?

Sorry, I do not understand you

Regards
Alex

Mikevirtu · Post by **Mikevirtu** » Wed May 20, 2015 6:54 am

May we see logs?
I log test on SQL server. it will be a little difficult:( I'll be think as it do.
When master test set Bad status? when dependant test set Bad status?
HostMonitor version?
I think it happens then master test Ok status. I now check it.
9.90

KS-Soft · Post by **KS-Soft** » Wed May 20, 2015 8:23 am

I log test on SQL server. it will be a little difficult:( I'll be think as it do.

some options:
a) select test item and press Ctrl+I, check Quick Log records
b) open Quick Log pane (HostMonitor menu View -> Quick Log), then select test item and check recent event in Quick Log pabe
c) SQL query to select test related records by ID or name...

Regards
Alex

Mikevirtu · Post by **Mikevirtu** » Thu May 21, 2015 12:59 pm

eventtime testname status reply testmethod testid agent
2015-05-21 21:41:54.000 Ping: 192.168.0.1 from HostMonitor Host is alive 8 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:41:51.000 Ping: 192.168.0.1 from HostMonitor Host is alive 11 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:41:42.000 Ping: 192.168.0.1 from HostMonitor Host is alive 9 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:41:39.000 Ping: 192.168.0.1 from HostMonitor Host is alive 8 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:41:27.000 Ping: 192.168.0.1 from HostMonitor Host is alive 9 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:41:23.000 Ping: 192.168.0.1 from HostMonitor Host is alive 8 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:09:09.000 Ping: 192.168.0.1 from HostMonitor No answer ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:08:57.000 Ping: 192.168.0.1 from HostMonitor Host is alive 10 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:08:54.000 Ping: 192.168.0.1 from HostMonitor Host is alive 12 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:08:51.000 Ping: 192.168.0.1 from HostMonitor Host is alive 14 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:08:45.000 Ping: 192.168.0.1 from HostMonitor Host is alive 12 ms ping (timeout - 1000 ms) 4726 HostMonitor
2015-05-21 21:08:41.000 Ping: 192.168.0.1 from HostMonitor Host is alive 9 ms ping (timeout - 1000 ms) 4726 HostMonitor

Mikevirtu · Post by **Mikevirtu** » Thu May 21, 2015 1:04 pm

and for dependent test I had
21.05.2015 21:09:23 No answer
for other test
21.05.2015 21:11:38 No answer

Parameters for master test (192.168.0.1) - Timeout 1000 Regular schedular 2 sec
Parameters for dependents test (192.168.0.8 and 17) - Timeout 2000 Regular schedular 1min

Consider status of the master test obsolete after 30 sec
Not Recheck dependant test items when master test status has been charged
Don't start more than 32 test per second

As result approximatly 400 message from tests - 200 No answer and 200 Host alive ok

KS-Soft · Post by **KS-Soft** » Thu May 21, 2015 1:32 pm

Yes, tests should not be performed.
May we see HML file with tests? Please send it to support@ks-soft.net

What happened between 21:41:23 - 21:09:09?
No records because master test return "no answer" status for 32 min and you are using Reply logging mode?

Regards
Alex

Mikevirtu · Post by **Mikevirtu** » Mon May 25, 2015 12:55 am

; ------- Test #01 -------

Method = Ping
;--- Common properties ---
DestFolder = Root\OFFICE\NETWORK\CISCO2901\
Title = Ping: 192.168.0.1 from HostMonitor
Comment = Ping 192.168.0.1
RelatedURL =
NamePattern = %methodname%: %host% from %agent%
CmntPattern = Ping %host%
ScheduleMode= Regular
Schedule =
Interval = 2
Alerts = Do nothing
Alerts2 =
ReverseAlert= No
UnknownIsBad= No
WarningIsBad= Yes
UseCommonLog= Yes
PrivLogMode = Reply
CommLogMode = Default
;--- Test specific properties ---
Host = 192.168.0.1
Timeout = 1000
Retries = 10
MaxLostRatio= 100
DisplayMode = time
DontFragment= No

Mikevirtu · Post by **Mikevirtu** » Mon May 25, 2015 12:55 am

Method = Ping
;--- Common properties ---
DestFolder = Root\OFFICE\NETWORK\CISCO2901\
Title = Ping: 192.168.0.8 from HostMonitor_1
Comment = Ping 192.168.0.8
RelatedURL =
NamePattern = %methodname%: %host% from %agent%_1
CmntPattern = Ping %host%
ScheduleMode= Regular
Schedule =
Interval = 60
Alerts = Do nothing
Alerts2 =
ReverseAlert= No
UnknownIsBad= No
WarningIsBad= Yes
UseCommonLog= No
PrivateLog = C:\ProgramData\HostMonitor\Logs\hosting.txt
PrivLogMode = Reply
CommLogMode = Default
SyncCounters= Yes
SyncAlerts = Yes
DependsOn = list
MasterTest-Alive = Ping: 192.168.0.1 from HostMonitor
;--- Test specific properties ---
Host = 192.168.0.8
Timeout = 2000
Retries = 4
MaxLostRatio= 100
DisplayMode = time
DontFragment= No

Mikevirtu · Post by **Mikevirtu** » Mon May 25, 2015 12:57 am

What happened between 21:41:23 - 21:09:09?
problem with internet channel
No records because master test return "no answer" status for 32 min and you are using Reply logging mode?
sorry, I don't undestand it

Mikevirtu · Post by **Mikevirtu** » Mon May 25, 2015 12:59 am

ip address for HostMonitor is 192.168.35.55

KS-Soft · Post by **KS-Soft** » Mon May 25, 2015 8:58 am

May we see HML file with tests? Please send it to support@ks-soft.net

Regards
Alex

Mikevirtu · Post by **Mikevirtu** » Tue May 26, 2015 1:56 am

I send results from SQL DB and parameters tests for situation on 2015.05.26 now.