Tuesday

SilkPerformer - How do I monitor a server in a remote location?

How do I monitor a server in a remote location?
Problem:

How do I monitor a server in a remote location?
Resolution:

SilkPerformer's Server Analysis Module (SAM) allows you to monitor data from remote servers in a straightforward manner, however in order to monitor any application through a firewall the correct ports must be opened. SAM can use one or more of the following methods / default ports to monitor applications and servers:


Windows - PerfMon - NetBIOS ports 137, 138, 139
UNIX - REXEC - Port 512
ALL - SNMP - 161

Should opening these ports pose an unacceptable security risk a workaround is to position an agent machine inside the firewall to do the monitoring (via monitoring scripts) and then access that machine in order to retrieve the monitor data. This can then be viewed alongside the test data on a machine outside the firewall.

Another possible workaround to this problem would be to have another MMC machine on the same side of the firewall of the machine that you are monitoring. You could then use SAM on this machine to monitor, the TSD file could be created and the data used in the normal way.

A further option which may be used for Windows is to use Perfmon to convert a binary PerfMon log to a CSV file and then convert/import CSV format to Time Series Data. For more information see 50150000000AFvv

Performance Explorer can also generate BDL monitoring scripts for server monitoring, which can be directly used by SilkVision and SilkPerformer. The advantages of monitoring scripts are:

*Monitors can be placed behind firewalls using a SilkPerformer remote agent
*Monitors can be directly integrated into load testing scripts
*Monitors scripts are the most flexible way to build sophisticated monitoring scenarios including event notifications, thresholds checks, or event-based monitoring.

How to generate monitoring scripts:
1. When Performance Explorer opens in "Server Monitoring" Mode select a data source to monitor.

2. Select the performance counter(s) to be monitored (with the "Data Source Wizard" it's easy to select the measurements you wish to have monitored).

3. Create a SilkPerformer BDL script for the active monitor graph BDL scripts can be generated at any time by either selecting
"FILE | GENERATE BDL SCRIPT..." from the menu bar or by selecting
"GENERATE BDL SCRIPT..." from the context menu in Monitor View's lower pane.

4. Specify a file name for the monitor script and save the file.

5. You will be asked to save Performance Explorer's workspace. Performance Explorer then closes and the script is added to your SilkPerformer project. The SilkPerformer window pops up, showing you the new monitor script.

6. Try Script - To verify the new monitor script, press the Try Script button on the workflow bar. The default update interval for collecting monitor data is 60 seconds.

7. You can adjust the monitoring interval by opening the Project Attribute Dialog
(SilkPerformer menu: PROJECT / PROJECT ATTRIBUTES) and changing the value of the "MeasureCollectionInterval" Attribute.

Note: Ensure that realistic values appear in the Virtual User Report File.

Some additional troubleshooting steps:
1 - When monitoring Windows machines SAM uses the same technology as Microsoft's Performance Monitor (perfmon), therefore if it is not possible to get data in perfmon it will not be possible to get values in SAM.

2 - If the server that you are attempting to connect to is behind a firewall. It may be the case that ports 137,138 and 139 need to be opened on this firewall. This may be something that you need to verify with the system administrator.

3 - In order to get Performance monitor data you need to have a valid network connection to the machine. To check this see if you can browse to the machine you are trying to monitor.

Borland ID: 5105 Author: Borland Created on: 37834 Product: Category:

No comments:

Post a Comment