How to: Manage Counter Sets Using the Load Test Editor
When you create a load test with the New Load Test Wizard, you add an initial set of counters. These offer you a set of predefined counter sets for your load test. For more information, see Step 3 - Specifying Counter Sets in the New Load Test Wizard.
Note
If your load tests are distributed across remote machines, controller and agent counters are mapped to the controller and agent counter sets. For more information about how to use remote machines in your load test, see Distributing Load Test Runs Across Multiple Test Machines Using Test Controllers and Test Agents.
Managing counter sets involves choosing the set of computers you want to collect performance data from, and assigning a set of counter sets to collect from each individual computer. You manage your counters in the Load Test Editor.
.png "Managing Counter Sets")
Requirements
- Visual Studio Ultimate
To manage counter sets
Open a load test.
Choose the Manage Counter Sets button.
– or –
Right-click Counter Sets folder in the load test tree and choose Manage Counter Sets.
The Manage Counter Sets dialog box is displayed.
(Optional) In the Selected computers and counter sets will be added under the following run settings list box, select a different run setting.
Note
This only applies if you have more than one run setting in your load test.
(Optional) Choose Add Computer to add a new computer to monitor. You will be prompted for a name. Type the name of a computer, and you will see nodes below the new entry. For example ASP.NET, IIS, SQL, and others. Select the check boxes in front of the nodes you want to select. The new counters appear in the Preview selections pane.
(Optional) In the Computer Tags text box, type a tag to associate with the computer. For example, "TestMachine12 in lab3".
Computer tags let you identify a computer with an easy-to-recognize name.
The tags are displayed in the Counter Set Mappings node in the tree in the Load Test Editor. More important, the tags are displayed in Excel reports, which help stakeholders identify what role the computer has in the load test. For example, "Web Server1 in lab2" or "SQL Server2 in Phoenix office". For more information, see Reporting Load Tests Results for Test Comparisons or Trend Analysis.
Choose OK.
See Also
Concepts
Specifying the Counter Sets and Threshold Rules for Computers in a Load Test
Other Resources
Distributing Load Test Runs Across Multiple Test Machines Using Test Controllers and Test Agents