I really need a Host field for every test method

Need new test, action, option? Post request here.
Post Reply
User avatar
greyhat64
Posts: 246
Joined: Fri Mar 14, 2008 9:10 am
Location: USA

I really need a Host field for every test method

Post by greyhat64 »

I'm bringing this up because of a specific situation.

I have a wonderful shell script which I will be posting in the library when it's ready, that will test a group of services and give an up/down status of the group. This is particularly handy when an application is dependant on the entire set of services for an 'UP' status (i.e. Crystal Reports, ArcServe, Backup Exec, Symantec EndPoint Protection, etc.).

But because I'm trying to run this on a remote machine I've spent the last week trying to debug script based remote authentication using the objLocator.ConnectServer method. I'm an admitted VBScript hack, so any code samples you can point me to would be appreciated. :) I've scavanged Tek-Tips (awesome forum site for virtually any tech topic) but I'm still beating my head against a wall.

I'm almost there, but wouldn't it be grand if EVERY test method allowed you to define it's host. At that point, it seems to me, that the features of Connection Manager could be extended to most, if not all, test methods, launching a session if the named host has a subsequent Connection Manager Profile and running the test after a connection has been established, or fail gracefully based on the 'CM' results.

I know I've barked about this once before, but it's a bit frustrating when some tests (UNC, process test, etc.) have a field specifically for the host (sometimes called Server, Address, URL, or something else), while others don't (Shell Script). Sometimes it's implied as local (File/Folder size), or it's buried in an expression (as with the Performance Monitor 'check counter' field).

In every one of these cases a field could be used to define the host, not only for the reasons listed above but also for the purpose of generating reports and performing advanced log analysis across test types based on the host. I know, at least from a reporting standpoint, I could use a Comment field, but isn't that just a workaround?

And while I'm still a big fan of the HM these suggestions aren't just based on my vision, but on the features I've seen/experienced with other similar products. I'm selfish and I want the HUGE strengths I see with HM AND the strengths I've seen elsewhere in one package. :wink:
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Regarding Connection Manager - it will not help you. HostMonitor cannot establish connection for your script because its not just some TCP connection between 2 systems. Its connection between 2 applications. E.g. your script needs access to remote registry, HostMonitor established such connection but object that you are using in the script does not know anything about HostMonitor and connection that were established by completely different object used in different application.

Regarding Host field - HostMonitor offers %HostAddr% variable. It represents the host name (or IP address) of the target system for the following tests: Ping, TCP, URL, HTTP, Oracle, Interbase, MS SQL, MySQL, Sybase, Postgre, Process, Service, NT Log, CPU Usage, SNMP, SMTP, POP, IMAP, DNS, DHCP, LDAP, UNC, UDP, NTP, RADIUS, Temperature Monitor, Traffic Monitor, Dominant Process
Probably we can extend its scope for Performance Counter, WMI, some other test methods. I have added your suggestion into list

Regards
Alex
User avatar
greyhat64
Posts: 246
Joined: Fri Mar 14, 2008 9:10 am
Location: USA

Post by greyhat64 »

Thanks, I guess I was looking for an easy way to address my frustrations with WMI connections. I think it stems from trying to connect across Windows versions.

Keep up the good work!
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Thank you.
BTW: We have extended scope for %HostAddr% macro variable in version 7.46 (not available yet). Now this variable can be used in actions triggered by Performance Counter, WMI, Mail Relay, Count Files, Text Log, Compare Files, File Integrity, Folder/File size, File/Folder Availability and Disk Free Space test methods (in addition to other 28 test methods that were supported earlier). When you are using this variable for file related test method, HostMonitor analyzes path to target file and returns name of target server or “localhost” when test item checks local file.

Regards
Alex
User avatar
greyhat64
Posts: 246
Joined: Fri Mar 14, 2008 9:10 am
Location: USA

Post by greyhat64 »

You just do these kind of things to evoke more praise comments, don't you? :lol:
Post Reply