We are currently running 2 instances of HostMonitor. One internally that performs most of our testing and one externally that performs additional tests as well as testing our internal HostMonitor. Occasionally we disable alerts on our internal HostMonitor when we are performing bulk server reboots as a result of applying MS patches.
On a couple of occasions we've forgotten to re-enable alerts after we were done. I'd like to be alerted once every hour when our alerts are disabled. I understand from reading some other posts that this wouldn't be possible with a single instance of HostMonitor. Is there a way we can configure our extenal HostMonitor to check if our internal HostMonitor's alerts are enabled or disabled?
I'd appreciate any suggestions.
Sincerely,
Alan Yabroudy
Alerting when alerts are disabled?
Correct. If you disable alerts, then HostMonitor does not start any alerts.
You may setup HostMonitor to execute alert profile when somebody just stopped alerts (menu Monitoring -> Pause)
Another solution:
1) setup "internal" HostMonitor to send SNMP Trap message to "exernal" HostMonitor everytime somebody enables/disables alerts. Use SNMP Trap "scheduled" action (Monitoring -> Pause -> Start action profile every time monitoring is stopped/paused + Start action profile every time monitoring is started/resumed)
2) setup "external" HostMonitor to react on these Trap messages using "SNMP Trap" test method
Regards
Alex
You may setup HostMonitor to execute alert profile when somebody just stopped alerts (menu Monitoring -> Pause)
If that instance has access to "internal" system, you may setup Compare Files test method to check for "AlertsDisabled=1" line in hostmon.ini fileIs there a way we can configure our extenal HostMonitor to check If your internal HostMonitor's alerts are enabled or disabled
Another solution:
1) setup "internal" HostMonitor to send SNMP Trap message to "exernal" HostMonitor everytime somebody enables/disables alerts. Use SNMP Trap "scheduled" action (Monitoring -> Pause -> Start action profile every time monitoring is stopped/paused + Start action profile every time monitoring is started/resumed)
2) setup "external" HostMonitor to react on these Trap messages using "SNMP Trap" test method
Regards
Alex