I was just wondering if there was a way to create one test that will go and test multiple computers. I am tryibg to test for the existance of an application running on multiple computers. I have set up a test for one machince to test for the existance of a process running and if not notify me at first bad and on second bad launch PSexec and start the application backup on the remote computer. I am going to have 20 -50 computres that run the same application, but really don't want to create a test for each computer. Can I create a master list that Hostmonitor can pull from?
Any help would be appreciated
Don
on test for Multiple computers
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
I do not think there is a way to monitor multiple computers with one test. However,you may use "Replicator" utility to make your life easier: http://www.ks-soft.net/hostmon.eng/replicator/index.htm You just should create a test for one computer, export it into text file (menu "File" -> "Export to text file") and use Replicator to populate tests for your 20 - 50 computers.
Regards,
Max
Regards,
Max
Max is right - you're probably better off setting up multiple tests within the context of AHM using the replicator tool.
But he's wrong, in the you could perform this as a single test using scripting or a called executable. I've done similar tests myself, but there are downsides. Getting the results and dealing with alarms appropriately from individual computers is not nearly as easy - you have to carefully construct your reply with a list of failing systems. You also have to deal with non-responsive computers in that reply. And if you have a number of non-responsive computers this can affect the overall performance of the system.
In the context of what you want to do, I dont' see that working well, but if you want a good source for, among other things, scripting tips join Tek Tips. It's my favorite source of, among other things, scripting solutions.
But he's wrong, in the you could perform this as a single test using scripting or a called executable. I've done similar tests myself, but there are downsides. Getting the results and dealing with alarms appropriately from individual computers is not nearly as easy - you have to carefully construct your reply with a list of failing systems. You also have to deal with non-responsive computers in that reply. And if you have a number of non-responsive computers this can affect the overall performance of the system.
In the context of what you want to do, I dont' see that working well, but if you want a good source for, among other things, scripting tips join Tek Tips. It's my favorite source of, among other things, scripting solutions.
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Correct. It's possible to implement this feature, but it requires additional efforts writing scripts or something else. Beside that, it might be difficult to support such kind of scripts, especially when servers are added or removed too often. That's why we do not recommend this approach. Nevertheless, everything is up to you.greyhat64 wrote:But he's wrong, in the you could perform this as a single test using scripting or a called executable.

Regards,
Max
Max,
That was exactly my point. AHM makes a lot of things possible, especially with the inclusion of scripting and external calls. But with that flexibility comes it's own complexities and issues. But when you said it couldn't be done I wanted to set the record straight.
In my case I had a group of services that could be dealt with as one. If any one fails, all of them need to be restarted in a particular order. My script makes that attempt and only triggers an alarm if that attempt is a failure. This probably could have been accomplished with individual tests and dependencies, but I wanted to test my newfound scripting skills. Plus, this way they are all consistently tested at the same time, where individual test schedules can get out of sync.
And if Don (dkurfurst) wants to go that route and he comes up with a good solution I look forward to seeing his entry in the Library. Then we are all the richer for the experience. (no pressure there Don
)
That was exactly my point. AHM makes a lot of things possible, especially with the inclusion of scripting and external calls. But with that flexibility comes it's own complexities and issues. But when you said it couldn't be done I wanted to set the record straight.
In my case I had a group of services that could be dealt with as one. If any one fails, all of them need to be restarted in a particular order. My script makes that attempt and only triggers an alarm if that attempt is a failure. This probably could have been accomplished with individual tests and dependencies, but I wanted to test my newfound scripting skills. Plus, this way they are all consistently tested at the same time, where individual test schedules can get out of sync.
And if Don (dkurfurst) wants to go that route and he comes up with a good solution I look forward to seeing his entry in the Library. Then we are all the richer for the experience. (no pressure there Don

-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Ok. Ok. You won.greyhat64 wrote:But when you said it couldn't be done I wanted to set the record straight.


That's correct, Don. We encourage everybody to post good solutions into "Library" branch in order to share experience between community.greyhat64 wrote:And if Don (dkurfurst) wants to go that route and he comes up with a good solution I look forward to seeing his entry in the Library. Then we are all the richer for the experience. (no pressure there Don)
Regards,
Max