In the Central list, select Monitoring
- Click the New Monitoring Server Group icon.The Monitoring Server / Monitor wizard appears.
Select Monitoring Server Group and click
Type a name for the Monitoring Server
Group and optionally provide a description. Click Next.
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.
The Hosts/Device Agents screen appears.
Note: The host(s) configured here should be the server(s) running Microsoft Windows.
- Select the version of Microsoft Windows to monitor. The Windows instance should be running on one of the listed hosts in the group AND CloudTest Conductor should be running on it.
- For Windows XP, WIndows Vista, WIndows Server 2003, Windows 7, and Windows 8 no additional configuration is required provided that the Conductor is running on the specified IP or host name running Windows. The port number is not used when monitoring Microsoft Windows (e.g. can be set to any value).
- On Windows Server 2008, you can use CloudTest Conductor as with other Windows versions. However, the additional option of a direct connection via WMI is provided. Refer to Prerequisites for DCOM/WMI Monitoring for WMI steps. Also, refer to Using the Windows Powershell Script for Remote WMI Access.
Connection. If the connection is successful, you will see the green
checkmark. If the connection fails, you will see an error message explaining what went
- Click Next and review the selected Summary and Resources for the server group.
Check Create a new Monitor
for this Monitor Server Group to create a monitor based on this server group
and then click Finish.
Enter a name for the new Monitor and an
optional description, and then click Next.
- Now, choose the statistics to monitor. For each statistic, you can choose a "sample rate" that 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
perfmoncommand). 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 Miniportand
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,
What you should see
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
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 Runningin the Arguments column.
When you are finished, click Next.
Review the information to be sure it is correct, then click Finish.