Work with SAM component monitors
Component monitors are the building blocks of SAM templates. Each template consists of multiple component monitors that are each designed to poll for specific metrics about an application, process, or event. Some component monitors have prerequisites, configuration, and credentials requirements for target systems, as listed in the SAM Template Reference.
To display the component monitors included in a template:
- Navigate to Settings > All Settings > SAM Settings >Manage Templates.
- On the Manage Application Templates page, click the Application Monitor Templates tab.
- Select an existing template and click Edit.
The following example shows some of the component monitors in the AppInsight for Active Directory template:
Component monitors that share similar characteristics are categorized by a component monitor type. The following example shows three different component monitor types included in the Active Directory 2016 Services and Counters template: Performance Counter Monitor, Windows Service Monitor, and Window Event Log Monitor.
Component monitor fetching methods
For many component monitors, you can configure the preferred fetching method used to gather data from target nodes. SAM automatically switches to a fallback method to collect data if the first method fails, and then works through other methods until polling succeeds.
You can also configure some component monitors to use Orion agents to collect data.
- Directory Size Monitors
- File Count Monitors
- Performance Counter Monitors
- Process Monitors for Windows
- Windows Event Log Monitor
- Windows Service Monitors
- WMI Monitors
To learn more about WinRM polling, see:
Component monitor thresholds
Some types of component monitors allow you to set threshold conditions on the monitored parameters. You can set separate thresholds to indicate warning and critical conditions. For example, to monitor the percentage of free space remaining on a volume, you can set a warning threshold at 15%, and a critical condition at 5%. To learn more, see Manage thresholds in SAM.
Component monitor scripts
Some component monitors gather data directly from target services, others execute scripts on target servers to pull metrics. For example, the Apache template uses an Orion agent and several Linux/Unix Script Monitors to collect data. The IdleWorkers component monitor uses SSH to upload a script to target Linux servers and then processes the returned values and text output that appear in the Orion Web Console.
The Active Directory 2016 Domain Controller Security template includes component monitors that use scripts to collect data:
- Locked out users uses a PowerShell script to pull metrics for currently locked out users.
- Disabled users uses a PowerShell script to return the number of currently disabled users; you can adjust thresholds as necessary.
Other topics in this section include:
- View the Component Monitor Library in SAM
- Manage component monitors in SAM templates and application monitors
- Edit component monitors in templates and application monitors
- Choose a fetching method for Performance Counter Monitors in SAM
- Use the Component Monitor Wizard in SAM
Additional resources include:
- SAM Custom Template Guide (Learn how to use component monitors in PowerShell, Nagios, Linux/Unix, and Windows scripts.)
- SAM Template Reference (Learn about component monitors included in predefined templates.)
- SAM Template Showdown (SolarWinds Lab Episode #53)
- Use PowerShell in SAM
- Use properties and variables in SAM application monitors and component monitors in alerts (SAM online help)