Choose a fetching method for Performance Counter Monitors in SAM
For many component monitor types, you can control the method that SAM uses to poll for data. For example, if you select WinRM/DCOM for a Windows Service Monitor, SAM will try to use WinRM for application polling. If WinRM fails, DCOM is used as the fallback method.
For Performance Counter Monitors, you can either:
- Select Default as the Fetching Method to allow fallback to occur when necessary, or
- Select one of the following methods for SAM to use explicitly:
- Managed (RPC): Calls .NET Framework methods to get performance counter data.
- External (RPC): Uses the CounterFetcher.exe utility to call the Performance Data Helper (PDH) API. Note that threading issues may occur with the PDH library, so multithreading polling jobs can cause polling failures.
- PDH (RPC): Calls the PDH API directly from the polling job.
- WMI: Uses WMI to collect performance counter data.
- WinRM: Uses WinRM to collect performance counter data. If WinRM fails, DCOM is used as the fallback method.
Starting in SAM 2020.2, WinRM is the default fetching method for WMI-based component monitors. For details, see Use WinRM for application monitor polling in SAM.
For more granular control of Performance Counter Monitors when Default is selected as the Fetching Method, advanced users can set the preferred order of fallback methods by editing the following file on the Orion server:
c:\Program Files (x86)\SolarWinds\Orion\APM\SolarWinds.APM.Probes.dll.config
For example, change the fetching order by editing the following line:
<add key ="PerfCounters.DefaultFetchingOrder" value="WinRM, Managed, WMI, External, Pdh"
Note that there are two properties in the
PerfCounters.DefaultFetchingOrderfor non-agent polled nodes.
PerfCounters.AgentModeFetchingOrderfor Agent polled nodes.
This function allows an administrator to change the priority of methods for application monitor templates, or for specific application monitors, as created when you assign a template to a specific node.