The Windows agent tracks CPU, memory, disk I/O, and network. Roughly two dozen metrics are collected automatically and integrated into the load-test reports, then plotted against response-time degradation. For .NET stacks, a dedicated agent adds about sixty ASP.NET, CLR, and IIS counters on top.
CPU, memory, and disk are captured in the Free edition on every monitored host. Network and TCP metrics, plus process queue length, are part of the Cloud full-metric set, alongside AWS CloudWatch and Dynatrace integration. The agent collects its full set automatically, with no metric-selection step to configure.
The base Windows metrics tell you what the box is doing. When the application is .NET, the dedicated .NET agent adds about sixty platform-specific counters on top: 27 from ASP.NET, 15 from the .NET CLR, 15 from IIS, and 5 from the combined web server process group. A request queue that climbs, a lock-contention spike, or a garbage-collection stall shows up against response time alongside the CPU curve.
The Analytics Dashboard plots every collected metric on the same x-axis as response time and flags any resource whose curve correlates above 0.94 with the slowdown. On Cloud the AI report writes the bottleneck-source paragraph from those flags: which resource saturated, on which host, at which user level the response time went vertical. Windows is the platform the Linux and AIX agents normalize to, so a mixed fleet compares directly in the same overview.
Run a load test against your Windows hosts and watch the metrics line up.
The monitoring agent ships in every WPLoadTester 7 install and captures CPU, memory, and disk for free. The full network, TCP, and .NET counter set is part of the Cloud edition. Download it to see your own server metrics correlated against response-time degradation.
Comparing tiers? See the Free vs Cloud split.