Need RMAs to perform actions
Need RMAs to perform actions
We are one of your enterprise licensees for Host Monitor and RMA manager. We have started using your RMA’s to monitor our proprietary application on servers all over the globe. We need the ability for the RMA agents to be able to perform some actions, or be instructed (By Host Monitor) to perform some actions on the remote machines. Specifically, we would like to test whether or not a process is running, and if the test is failed, to restart a service that will reinitialize that process. Please let us know if that is possible with your software. If you require further detail, please email us or call Mike Parrella at 203-246-6261 at your convenience.
RMA cannot perform actions yet, this functionality will be implemented in future versions.
However I see simple workaround that will help in your case - setup additional "External" test.
E.g.
- if you have TestA that checks whether or not process is running, create another "External" test (TestB) for the same RMA. TestB (for example) can start simply BAT file "NET STOP service_name NET START service_name".
- by default TestB should be disabled!
- test interval for TestB should be longer than test interval for TestA.
- now you just need to add 2 actions (1 "bad" action, and 1 "good" action) into action profile that is assigned to TestA
1st "bad" action should execute HMScript with single command "EnableTest TestB"
2nd "good" action should execute HMScript with single command "DisableTest TestB"
That's it.
Now if TestA fails, it will enable TestB that in turn will execute BAT file on the remote system. When TestA detects that process is running, it will disable TestB (to avoid unnecessary restarts of the service).
Regards
Alex
However I see simple workaround that will help in your case - setup additional "External" test.
E.g.
- if you have TestA that checks whether or not process is running, create another "External" test (TestB) for the same RMA. TestB (for example) can start simply BAT file "NET STOP service_name NET START service_name".
- by default TestB should be disabled!
- test interval for TestB should be longer than test interval for TestA.
- now you just need to add 2 actions (1 "bad" action, and 1 "good" action) into action profile that is assigned to TestA
1st "bad" action should execute HMScript with single command "EnableTest TestB"
2nd "good" action should execute HMScript with single command "DisableTest TestB"
That's it.
Now if TestA fails, it will enable TestB that in turn will execute BAT file on the remote system. When TestA detects that process is running, it will disable TestB (to avoid unnecessary restarts of the service).
Regards
Alex