Configuration: Systems Under Test: PerfCounter Settings
Overview
Use this page to configure per-machine performance counter settings. A performance counter is a measurement, such as CPU or memory usage, that the platform collects from a machine's operating system while it is monitored or under test. This page is where you tell the platform which machines to collect counters from, what credentials to use when connecting to them, and whether collection is currently active.
Each entry here is keyed to a machine that already exists as a system under test, configured on Configuration: Systems Under Test: Machines. Credential Profile values reference profiles created on Configuration: Credential Profiles, so the platform can authenticate to the machine without you re-entering credentials every time. Once collection is active for a machine, the counters it gathers are measured in the units defined on Configuration: Systems Under Test: Counter Units.
From this page you can review every machine currently configured for performance counter collection, add a new machine entry, edit an existing machine's operating system, credential profile or active state, and delete entries you no longer need.
Key concepts
- performance counter - A measurement, such as CPU or memory usage, that the platform collects from a machine's operating system during monitoring or test runs. (related: Configuration: Systems Under Test: Counter Units)
- credential profile - A stored set of authentication credentials that lets the platform connect to a machine without you re-entering a username and password for every entry. (related: Configuration: Credential Profiles)
- system under test machine - A machine registered with the platform as a target that is monitored or tested. (related: Configuration: Systems Under Test: Machines)
- collection active - The on/off state controlling whether the platform currently gathers performance counters from a given machine.
When to use it
- You're onboarding a new system under test machine and need to enable performance counter collection for it.
- A machine's recorded operating system or credential profile is out of date and its counter settings need correcting.
- You need to temporarily stop counter collection on a machine, for example during maintenance, without deleting its configuration.
- You're decommissioning a machine and need to remove its performance counter settings.
- You're troubleshooting missing performance counter data and want to confirm a machine is marked Active with the correct credential profile.
Before you begin
- The machine must already exist as a system under test machine, configured on Configuration: Systems Under Test: Machines.
- If you plan to assign a credential profile, it must already be created on Configuration: Credential Profiles.
- Your account must hold a role with write access to this page; without it, New Entry, Edit and Delete controls are hidden.
Common workflows
Add performance counter settings for a new machine
Persona: load-test operator or admin
- Select New Entry.
- Expect: An editor opens with empty Machine Name, Operating System and Credential Profile fields and an unchecked Collection active checkbox.
- Enter the machine's name in Machine Name, optionally fill in Operating System and Credential Profile, and check Collection active.
- Expect: The typed values appear in their fields and the Collection active checkbox shows as checked.
- Save the entry.
- Expect: The editor closes and the new machine appears as a row in the table with an Active status badge.
Verify: The new machine name appears in the table with the Operating System, Credential Profile and Active status you set.
Edit an existing machine's counter settings
Persona: load-test operator or admin
- Select the pencil Edit icon on a machine's row.
- Expect: The editor opens pre-filled with that machine's current Operating System, Credential Profile and Collection active value.
- Update the fields you want to change and save.
- Expect: The editor closes and the row reflects the updated values.
Verify: The edited row shows the new Operating System, Credential Profile, or Active status without a duplicate row being created.
Remove a machine's performance counter settings
Persona: load-test operator or admin
- Select the trash Delete icon on a machine's row.
- Expect: A Delete Entry confirmation dialog opens asking you to confirm removal.
- Select Delete in the confirmation dialog.
- Expect: The dialog closes and the row is removed from the table.
Verify: The deleted machine no longer appears in the table; configuring it again requires adding a new entry with New Entry.
Steps
Step 1
Open Performance Counter Settings.
Expected result: The page loads showing a table of per-machine performance counter entries for CTX-DDC01.CORP.EXAMPLE.COM, CTX-VDA01.CORP.EXAMPLE.COM and SQL01.CORP.EXAMPLE.COM, each listing its Operating System, Credential Profile and Active status. A Credentials expiring banner also appears in the top-right, noting that the Orders API token expires in 4 days.
This is the starting view for reviewing which machines currently have performance counter collection configured.
- The Credentials expiring banner links to Configuration → Credential Profiles, not to this page's settings.
- Each row's MACHINE NAME is shown in link-style formatting.
-
ACTIVE shows Active for all three listed machines.
Step 2
Select Refresh.
Expected result: The table reloads with the same three machine entries, and the Credentials expiring banner is no longer shown, fully revealing the Refresh and New Entry buttons in the header.
Refreshing confirms you're viewing the current set of performance counter entries before adding or editing one.
- New Entry opens the editor to add a machine.
- Each row's pencil and trash icons remain available for Edit and Delete.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Machine Name | Identifies the system under test machine this counter configuration applies to. It must match the machine's registered name so the platform associates counter collection with the correct host. | text (hostname or FQDN) | Yes | - |
| Operating System | Records the OS family running on the machine. It is free text rather than a fixed list, so use consistent values (for example always 'Windows') to keep the column readable and comparable across entries. | text | No | - |
| Credential Profile | References a stored credential profile the platform uses to authenticate to the machine. Leave it blank if no credentials are needed; set it to reuse a profile instead of storing credentials separately for this entry. | text (credential profile name) | No | - |
| Collection active | Turns performance counter collection on or off for this machine. Uncheck it to pause collection, for example while a machine is in maintenance, without losing the configured operating system and credential profile; check it to resume collection. | checkbox | No | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| MACHINE NAME | - | Identifies which machine the row's settings apply to; it is shown in link-style formatting. |
| OPERATING SYSTEM | - | Shows the OS family recorded for the machine, as entered in the editor. |
| CREDENTIAL PROFILE | - | Shows which credential profile is assigned to the machine, or is blank if none is set. |
| ACTIVE | - | Active (green badge) is the only state observed in current entries; it reflects the Collection active checkbox being checked for that machine. |
| ACTIONS | - | Provides the Edit and Delete icon buttons for that row; it does not display a data value itself. |
Controls reference
Refresh
Reloads the performance counter settings table from the server.
When to use: Use to confirm you're viewing the latest entries, for example after another admin may have changed one.
Side effects: Read-only: no entry data is changed. In this capture, using it also cleared the Credentials expiring banner, revealing the Refresh and New Entry buttons it had been covering.
New Entry
Opens an empty editor to create a performance counter settings entry for a machine.
When to use: Use when a system under test machine needs performance counter collection configured for the first time.
Side effects: Mutating once saved: creates a new row in the table. Selecting Cancel in the editor discards the entry and makes no change.
Create First Entry
Opens the same empty editor as New Entry, shown in place of the table when no entries exist yet.
When to use: Use on a newly configured instance, or after deleting all entries, to create the first machine's counter settings.
Side effects: Mutating once saved; same create behavior as New Entry.
Edit (icon)
Opens the editor pre-filled with the selected machine's current Operating System, Credential Profile and Collection active value.
When to use: Use to correct a machine's recorded operating system or credential profile, or to turn its collection on or off.
Side effects: Mutating once saved: updates the existing row in place, using the original machine name as the key. Selecting Cancel makes no change.
Delete (icon)
Opens a Delete Entry confirmation dialog for the selected machine's row.
When to use: Use when a machine no longer needs performance counter collection configured, for example after decommissioning it.
Side effects: Read-only by itself; it only opens the confirmation dialog. No row is removed until you confirm Delete inside the dialog.
Cancel (editor)
Closes the New Entry or Edit editor without saving.
When to use: Use if you opened the editor by mistake or decide not to proceed with the change.
Side effects: Read-only: discards any typed values; no row is created or changed.
Delete (confirmation dialog)
Permanently removes the selected machine's performance counter settings entry.
When to use: Use after confirming in the Delete Entry dialog that you want to remove this machine's entry.
Side effects: Mutating and irreversible: the row is removed from the table immediately after confirmation.
Close (banner)
Dismisses the Credentials expiring banner.
When to use: Use to clear the notification once you've noted it, or after reissuing the referenced token.
Side effects: Read-only: only hides the banner; it does not affect the token or any table entry.
Verify the result
After saving a new or edited entry, the table shows a row for that machine with the Operating System, Credential Profile and Active status exactly as you entered them. When editing, the row updates in place under the original machine name rather than creating a duplicate row. If a save fails, an Error message appears above the table instead of the editor closing, and the entry list stays unchanged. If the change doesn't seem to take effect, check that Machine Name is filled in, since it is the only required field.
Troubleshooting
- Symptom: The New Entry, Edit and Delete controls are missing entirely. Fix: This is a permission-based hide, not an error; your account lacks the write role for this page. Ask an admin to grant it under Operations: Permissions.
- Symptom: Saving an entry shows an Error message and the editor stays open. Fix: Confirm Machine Name is filled in, since it's the only required field, then retry.
- Symptom: The Credentials expiring banner keeps appearing on this page. Fix: It's unrelated to the entries in this table; reissue the referenced token under Configuration: Credential Profiles, then dismiss the banner with Close.
- Symptom: The table shows 'No machine entries'. Fix: No performance counter settings exist yet; select Create First Entry (or New Entry) to add one for a system under test machine.
- Symptom: A machine's counters aren't being collected even though its row shows Active. Fix: Verify the Credential Profile name matches a profile configured on Configuration: Credential Profiles exactly; a mismatched or missing profile can prevent authentication.
Related articles
- Prerequisite: Configuration: Systems Under Test: Machines - a machine must be registered as a system under test before you can configure its performance counter settings
- Prerequisite: Configuration: Credential Profiles - the Credential Profile field references profiles created there
- Next step: Configuration: Systems Under Test: Counter Units - defines the measurement units for the counters you enable here
- See also: Operations: Permissions - controls whether your account can see the New Entry, Edit and Delete controls on this page