The new Traffic Monitor is a Great feature. . Can you please add Interface Status also as a parameter for alert ? At the moment, I am having separate SNMP tests feeding the different OIDs.
Also, before a test is declared bad, can it perform the master test again rather than depend on the last result ? This would raise a more precise alert and we can just give one preceeding test as master test.
Can you please add Interface Status also as a parameter for alert ? At the moment, I am having separate SNMP tests feeding the different OIDs.
We have this task in "to do" list.
Also, before a test is declared bad, can it perform the master test again rather than depend on the last result ? This would raise a more precise alert and we can just give one preceeding test as master test.
I think new option could be useful but for now you may set "Consider status of the master test obsolete after N seconds" option = 2 sec. In this case master test will be performed before any dependant test.
New features of the latest release touches the below topic I had raised long ago.
"As you know "Consider status of the master test obsolete after N seconds" option tells HostMonitor for how long a Master test status is considered to be up-to-date. If Master test was performed more than N seconds ago, HostMonitor will recheck the Master test item before checking dependant items."
Along with the above, am once again requesting for the option I had raised earlier. Let the test be performed irrespective of the status of the master test. If the result is bad, i feel below steps would be much better.
1. Result = Bad.
2. Do not declare the result as bad immediately. Put it on temporary hold.
3. Perform its 'Master test".
4. Depending on the Master test result, then declare the appropriate result.
This would help better in Root Cause Analysis and raise a more precise alert. And also reduces number of times Master tests are performed, which has many other benefits like reduced logs etc.
I have around 500 tests (combination of ping & file compare) that depend on the VPN gateway (Master) to be alive. Each test is performed every 2 mins. This means, almost every 2 or 3 seconds the VPN gateway is polled. Logs get large and messy and also unnecessarily executing master tests even if dependant is alive. This is just one example of reducing unnecessary overheads.
Agreed. It may not be critical for you. That is why am still posting it in the Wish List for the last 2 1/2 years !! You may end this discussion if you didn't like what I am asking. I will still continue to use Host Monitor.
Logs get large and messy and also unnecessarily executing master tests even if dependant is alive.
You may easily change log setting, e.g. use "Brief" logging mode for this test. If you need some statistics, you may disable log and use "Record HM log" action instead, e.g. record result every 5th test + record result when test status changes.
Agreed. It may not be critical for you. That is why am still posting it in the Wish List for the last 2 1/2 years !! You may end this discussion if you didn't like what I am asking.
I cannot say I don't like this idea. This is medium priority task. Right now we are working on task that was requested by 20-30 customers.
Lets vote? If a lot of people need this option, I will change priority to "high"
. Can you please add Interface Status also as a parameter for alert ? At the moment, I am having separate SNMP tests feeding the different OIDs.
