RMA agent test to use for dependencies
-
- Posts: 15
- Joined: Thu Mar 05, 2009 5:50 pm
RMA agent test to use for dependencies
I recently had an issue where an active agent wasn't able to connect to the master Hostmon instance, and all the alerts using the agent alerted en masse. I want to create a dependency so that if the agent is unavailable, there is ONE test that ONLY looks at the agent connectivity, and then make all the tests that use that agent dependent on that alert. How can I accomplish this ?
-
- Posts: 15
- Joined: Thu Mar 05, 2009 5:50 pm
My active RMA agent was unable to connect to Hostmon, and all the tests using the agent spammed alerts saying:
RMA not connected is Unknown
Now, in this case, it was user error (Hostmon was running as a service, and someone started another instance as an application). So essentially, one instance was properly connected to the RMA agent through the specified port, but the other was blocked due to the port being in use.
I thought the best way to trim the # of alerts was to use a master test for a dependency (in the event of a legitimate alert of the RMA agent truly not being able to connect for a real reason), but I don't know how to select the RMA agent itself as a master test. I'm trying to do it now by setting up an 'HM Monitor' alert, and pointing at the system running the RMA agent, but it isn't seeming to work. I'm guessing there is another place/way to set up alerting for RMA agents?
RMA not connected is Unknown
Now, in this case, it was user error (Hostmon was running as a service, and someone started another instance as an application). So essentially, one instance was properly connected to the RMA agent through the specified port, but the other was blocked due to the port being in use.
I thought the best way to trim the # of alerts was to use a master test for a dependency (in the event of a legitimate alert of the RMA agent truly not being able to connect for a real reason), but I don't know how to select the RMA agent itself as a master test. I'm trying to do it now by setting up an 'HM Monitor' alert, and pointing at the system running the RMA agent, but it isn't seeming to work. I'm guessing there is another place/way to set up alerting for RMA agents?
You cannot select agent as master test because master test is a test but you can easily create test that will check agent.but I don't know how to select the RMA agent itself as a master test
E.g. use Ping test.
Quote
====================
Ping test provides option for immediate Active RMA status request. Yes, you could setup "Ping localhost" test to check agent status. However this may lead to some delay in reaction as HostMonitor will not perform test if agent was connected but lost connection just a moment ago. HostMonitor may wait up to several minutes for new connection before changing test status to "Unknown". If there are some dependant test items, these tests will be delayed as well so such delay is not a big problem. However if for some reason you need to receive alert immediately, now there is solution: setup Ping test using Active RMA and type rma itself string instead of localhost or target host name. In such case HostMonitor will display agent status immediately. HostMonitor will not use backup agent (if any) when specified agent is not connected; also HostMonitor will not wait for re-connection request from the agent.
====================
HM Monitor alert? Do you mean "HM Monitor" test method? It has nothing to do with RMA.I'm trying to do it now by setting up an 'HM Monitor' alert
Please check the manual: http://www.ks-soft.net/hostmon.eng/mfra ... #hmmonitor
Regards
Alex
-
- Posts: 15
- Joined: Thu Mar 05, 2009 5:50 pm