The Windows agent gathers data by using Windows performance counters. When the Monitoring Station polls the up.time Uptime Infrastructure Monitor agent, the agent requests the required data from the performance counters, parses the appropriate information and returns the requested information to the Monitoring Station.
| Table of Contents |
|---|
Since the up.time Because the Uptime Infrastructure Monitor agent uses the performance counters to collect statistics, the memory consumed by the Windows counters is associated with the up.time Uptime Infrastructure Monitor agent binary. However, the memory is actually being consumed by the Windows operating system, which maintains the built-in performance counters.
Memory usage is generally only noticeable in large systems that are running hundreds of processes at any given time. The up.time Uptime Infrastructure Monitor agent registers the process performance counter that stores historical data for each process. Storing this information causes the RSS and memory size to increase so as the number of processes running on the system grows, the memory size and RSS will follow accordingly.
This scenario can be demonstrated by using standard Windows performance tools. Running perfmon.exe and loading all the appropriate process counters will recreate the same memory variant that you see with the up.time Uptime Infrastructure Monitor agent because the agent uses the same counters. The permon.exe utility will spawn a child process (mmc.exe) that will show the memory being consumed by the performance counters.
...
Load perfmon.exe and add the counters listed below. After the counters have been successfully added, you can use up.time Uptime Infrastructure Monitor to monitor the memory usage growth.
...