Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on
01-28-2019
04:24 PM
- edited on
03-24-2021
03:56 PM
by
Claudia.Landiva
How do I solve performance issues when collecting metrics with the Windows Machine Agent?
Some users have experienced slow performance and/or high resource consumption when collecting server metrics on Windows with Server Visibility enabled.
The ServerMonitoring extension uses theWindows Management Instrumentation (WMI) to collect metrics on Windows machines. If you experience problems using WMI, you can configure the ServerMonitoring extension to use SIGAR instead.
The trade-off is that SIGAR cannot collect all the metrics that WMI can. See What metrics are not available when using SIGAR?, below for the list. In addition, this solution is available only on version 4.3.8 (or higher) of the Machine Agent.
To use SIGAR, specify the following System Property on the agent (the default is false
)
-Dappdynamics.machine.agent.extensions.sim.sigarCollectorEnabled = true
If you use SIGAR (not WMI) with the ServerMonitoring extension, the following metrics will be unavailable.
Bumped into WMI failing every 20 minutes on Windows Server 2012 R2 due to https://docs.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/high-cpu-u...
which provides a decent description of the reasoning behind the WMI timeouts occurring on a regular basis.
WMI stands for Windows Management Instrumentation not Monitoring Interface as above.
@Karen.Isaakyan , Thank you for sharing the Windows documentation, as well as pointing out the incorrect acronym. We appreciate it!
We'll get that revised in the article.
The acronym now reads as standing for Windows Management Instrumentation.
Claudia Landivar
Community Manager & Editor
Continuing on investigating the timeouts I've figured out they're due to appd collector.vbs script using WMI to query the following classes:
Win32_PerfRawData_PerfDisk_LogicalDisk
Win32_PerfRawData_Tcpip_NetworkInterface
Win32_PerfRawData_PerfOS_System
Is there any chance Appd SIM Extension will move to PDH (Performance Data Helper) instead of WMI, following the OSHI path: https://github.com/oshi/oshi/issues/505
Karen,
The newer version of AppDynamics Machine Agent (with SIM) has already moved away from using WMI to OSHI libraries already for Memory, CPU and Process metrics starting from v4.5.17.
For the network, disk and OS metrics, we still continue to use WMI, which we agree that has performance issues. AT this point, there is no plan for the machine-agent to use PDH.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form