Monitoring Microsoft Windows

Document created by Chris Sommerstad Employee on Jul 22, 2017Last modified by Dave Murphy on Sep 26, 2017
Version 3Show Document
  • View in full screen mode

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

  1. In the Central list, select Monitoring Server Groups.

  1. Click the New Monitoring Server Group icon.

The Monitoring Server / Monitor wizard appears.

  1. Select Monitoring Server Group and click Next.

  1. 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.

  1. 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.

  1. Select the version of Microsoft Windows to monitor. The Windows instance should be running on one of the listed hosts in the group AND SOASTA 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).

    1. Click the Test 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 wrong.

    1. Click Next and review the selected Summary and Resources for the server group.
    2. Check the "Create a new Monitor for this Monitor Server Group" box to create a monitor based on this server group and then click Finish.

    1. Enter a name for the new Monitor and an optional description, and then click Next.

    1. 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 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.

    Note: Use the Name (Optional) column to give the metric a user-friendly label that shows up in the widget's title bar.

    When you are finished, click Next.

    Review the information to be sure it is correct, then click Finish.

    Next steps

    You can also combine database, J2EE, and ColdFusion statistics in the same monitor.

Attachments

    Outcomes