Monitoring Microsoft Windows - CloudLink

Monitoring Microsoft Windows

by

Community Manager

on - last edited on

Prerequisites In order to monitor a Microsoft Windows server, the SOASTA Conductor application must be installed on the server. For more information, see the topic "Installing SOASTA Conductor".
Steps In the Central list, select Monitoring Server Groups.
Click the New Monitoring Server Group icon. The Monitoring Server / Monitor wizard appears:
Select Monitor Server and click Next. The Name and Connection step is shown.
Type a name for the Monitoring Server and optionally provide a description. Finally type the hostname or IP address of the server into the Host field and click Next. If SOASTA Conductor will be an agent for Windows monitoring, use only the hostname. Note: When Conductor is being used for Windows Monitoring, CloudTest specifically looks for a Conductor whose host name matches the server being monitored. CloudTest doesn't store the IP address for Conductors, so entering an IP address will not produce a match.
The Resources step is shown. Check "System Resources" and click Next.
Select the version of Microsoft Windows being monitored, then select the name of the SOASTA Conductor running on the server. It is important to select the correct Conductor name. The port number is not used when monitoring Microsoft Windows (can be set to any value).
Click the Test Connection button to test the connection. If the connection is successful, you will see a pop-up containing some information about the Windows server. If the connection fails, you will see an error message explaining what went wrong.
Click Next.
Review the information to be sure it is correct, then check the "Create a new Monitor for this Monitor Server" box and click Finish.
Enter a name for the Monitor and an optional description, and then click Next.
At this point you can choose which statistics you are interested in. For each statistic, you can choose a "sample rate" which determines how often that statistic will be collected. Some of the statistics require an entry in the "Arguments" column. For example: For the "Network KBits Received" and "Network KBits Sent" statistics, you must enter the name of the network interface you want to monitor. To find the list of available network interface names, you will need the ability to access the Performance management console on the Windows server being monitored. To get to the Performance management console, open the Control Panel, then open Administrative Tools, then open the Performance applet (alternatively, you can run the `perfmon` command). Right-click inside the graph and choose "Add counters..." In the dialog that appears, change the "Performance object" drop-down to "Network Interface", and look at the list that appears on the right. Some examples of network interface names are `Intel[R] PRO_1000 PL Network Connection - Packet Scheduler Miniport` and `Realtek RTL8029[AS] PCI Ethernet Adapter - Packet Scheduler Miniport`. For the "Per Process CPU Percentage", "Per Process Memory Usage", "Per Process Thread Count", and "Per Process Virtual Memory" statistics, you must enter the name of a process (for example, `inetinfo` or `sqlservr`).
In addition to the standard statistics, you can track the value of any Windows performance counter. For example, to track the number of thread context switches per second, check the "Performance Counter" box, and enter `\Thread(_Total/_Total)\Context Switches/sec` in the "Arguments" column. You can use the "Add Custom Object" button to add as many performance counters as you like. Some more examples: To track the amount of memory being used by the Microsoft SQL Server database cache, enter `\SQLServer:Memory Manager\SQL Cache Memory (KB)` in the "Arguments" column. To track the amount of current number of ASP.NET 2.0 worker processes, enter `\ASP.NET v2.0.50727\Worker Processes Running` in the Arguments column.
When you are finished, click Next. Review the information to be sure it is correct, then click Finish.
Next steps To start or stop monitoring, see Starting and Stopping a Monitor To automatically monitor the Windows server every time a certain test starts, see the topic Starting a Monitor Automatically When a Test Composition Runs You can also combine database, J2EE, and ColdFusion statistics in the same monitor.