| Thincomputing.net Exclusive: ProactiveWatch 1.4 Sneak Preview |
| Friday, 26 May 2006 by Michel Roth | |||
|
Revamped Client and Server Latency Testing Model Currently the LAN column in the Explorer refers to a latency measurement between a Client Agent, and a Gateway. This presumes that the Clients are on the same LAN as the Servers and the Gateway, and is therefore not optimal for WAN connected clients (which are by their nature more likely to have latency issues anyway). Currently the only way to measure the latency between a Client Agent and a Citrix Server is to install a Gateway upon the Citrix Server, which is both illogical and cumbersome. Netstat Port Monitoring Server Agents will have the ability to listen for ports. This will include the ability to check ports that are supposed to exist and work, and a list of banned ports that are not supposed to exist. Monitoring of both TCP and UDP ports will be supported. This will allow, for example, a simple monitor to be set up to ensure that the SQL Server port is in fact functional and that no one has brought up a FTP server on the network. Service Change Monitor Currently in order to monitor a specific service to see if it goes down that service name must be manually entered into the Advanced configuration of the Monitoring Templates. In ProactiveWatch 1.4 an additional option will exist to automatically monitor all services that are set to start automatically to see if they go down. Notification Policies The granularity and sophistication of email notifications is being greatly expanded in this release. It will now be possible to create Notification Policies that precisely map to the business rules in the VAR’s support agreements with the VARs customers. This will include control of which alarms are in which class of severity, during what days and times of day the notifications should be sent, and the chain of people that an alarm should be sent to as the alarm escalates. Enhancement to Alarm Notification Emails Email Alerts will include Customer Name, Alarm Number and VAR Full Name and not just the VAR ID Account For Time Zones In Alarm Notifications The Explorer will have an options dialog that will allow the VAR to select their Time Zone. All alarms from Servers and Notifications via email will be normalized to this Time Zone. This will ensure that alarms from distributed servers are understood correctly in terms of the actual time at which the Alarm occurred, and give users who are getting email notifications a common point of reference as to when the notification actually occurred. Note that the notifications will use the Time Zone chosen by the VAR, so if the recipient is remote to the chosen Time Zone alarms will be offset by the number of hours that separate the chosen Time Zone from the Time Zone in which the recipient is currently residing. Published Applications Compare ProactiveWatch currently supports System Compare and Applications Compare where Applications Compare Compares the existence and versions of installed applications. ProactiveWatch 1.4 will add the ability to compare Published Applications across servers allowing admin’s to easily identify inconsistencies in published applications between servers that are supposed to be the same. Agent Troubleshooting and Configuration Tool ProactiveWatch 1.4 will ship with a tool that will allow Agent configuration to be tested and changed from within an easy to use GUI. It will no longer be necessary to edit a text file to change configuration parameters for agents.
Show/Hide comment form
 |
|||
