I would recommend you to have more execution servers... OR.. create a custom monitor in Workbench that would run these ping checkers.
Consider the code below (I just customize a code that I have to serve you... may need some tweak...)
Attached you have the custom include file.. I use that to have friendly names into my custom counters. (I mean.. add the execution server name into custom measures).
@codepage(1252) benchmark BMCTMARTRecorder use "WebAPI.bdh" use "GetMyLocation.bdh" dcluser user VUser transactions TInit : begin; TMain : 1; var dclrand dcltrans transaction TInit begin // // WebSetBrowser(WEB_BROWSER_MSIE7); // WebModifyHttpHeader("Accept-Language", "en-US"); // //WebSetUserBehavior(WEB_USERBEHAVIOR_FIRST_TIME); // //WebSetDocumentCache(true, WEB_CACHE_CHECK_SESSION); end TInit; transaction TMain var aHost : array  of string(70); // resize this as you need aTitle : array  of string(40); // resize this as you need sLocation : string; nId : number; sCounterName : string; begin aHost:="192.168.10.196"; //.... add here as many hosts you need. aHost:="192.168.10.190"; aHost:="192.168.10.120"; aTitle:="Custom Host Name"; //.... give them friendly names! :-) I love friendly names. aTitle:="Custom Host Name 2"; aTitle:="Bonaco Box"; GetMyLocation(sLocation); // Custom Include to add a Friendly Execution server name into the Counter Name. for nId:=1 to 3 do // ====> The final number should be equal to the number of hosts you have. sCounterName:=aTitle[nId]+"-"+sLocation; MeasureStart(sCounterName); WebPing(aHost[nId]); MeasureStop(sCounterName); if not WebPing(aHost[nId]) then Print("Host "+aTitle[nId]+" is not responding") else Print("Host "+aTitle[nId]+" is alive") end; if not WebPing(aHost[nId], 500, 1) then Print("Host "+aTitle[nId]+" is not responding") else Print("Host "+aTitle[nId]+" is alive") end; end; end TMain;
Let me know your thoughts about it...
GetMyLocation.bdh.txt 833 bytes
Flavio Bonacordi is on the right track here.
There is a limit to the number of active monitors. An active monitor is one that has an active schedule, and thus will have a running copy of perfRun.exe If all the monitors are Pings or URL Checkers or other very lightweight web scripts, you can push up to the high end of the limit, about 200.
But you really might want to do something like what Flavio has suggested, create a fairly simple script to ping a group of servers in a loop. Instead of a Print, you might want to wrap the ping in a Custom Timer named for the IP address or hostname. And if you're feeling very creative, you could even load the list of hosts from a file for easy maintenance.
Thank you Hal and Flavio.
This sounds like a really good approach, particulary if we are able to set up an easliy maintainable file containing the severs to be pinged. My assupmtion is that the serve list will broken down into manageable groups. Again, my thanks to both of you. I'll let you know of any progress.
Happy to help.
You might want to look over some of Flavio's and my posts in this discussion thread
It's a different use case but the ideas for file handling would still be applicable.