Work with component monitors in SAM templates
Component monitors are the building blocks of SAM templates. Each template consists of multiple component monitors designed to poll for specific metrics about an application, process, or event.
For example, here are two component monitors included in the Active Directory 2016 Domain Controller Security template:
- The "Locked out users" monitor utilizes a PowerShell script to pull metrics for currently locked out users.
- The "User Account: User account was created" monitor scans Windows event logs for events that match certain criteria (for example, events that contain a specific keyword).
Component monitors like these two are designed to poll for application data — in this case, Active Directory — so you may also hear them called "application monitors."
Some component monitors pull hardware-related metrics. For example, the OOTB Apache template includes a "ServerUptime" monitor that uses SSH to upload a script to a Linux/Unix server and retrieve server uptime metrics for an Apache server. For a list of available monitors, see SAM component monitors.
To learn more about SAM templates and component monitors, see
- Manage application monitor templates in SAM
- Monitor with Orion agents in SAM
- Modify templates, application monitors, and component monitors in SAM
- SAM Custom Template Guide
- Configure Linux/Unix systems for SAM templates and component monitors
- Use the Component Monitor Wizard
- Create custom component script monitors
- Understand application monitor thresholds
- Example tasks for application monitors
Component monitors are the building blocks of SolarWinds SAM. Each monitors the status and performance of a different aspect of an application. There are several different types of component monitors, each containing settings that define what is monitored and how to monitor it.
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, if you are monitoring the percentage of free space remaining on a volume, you can set a warning threshold at 15%, and a critical condition at 5%.
As an analogy, pretend SolarWinds SAM is monitoring a car. You would have component monitors to check tire pressure, engine RPM, water temperature, battery voltage, and other important subsystems of that vehicle. You can set alerts to give notification if the water gets too hot, or if the battery voltage drops too low.
Application Monitor Templates
A template is a group of component monitors modeling the total availability and performance level of an application. A complicated application such as Windows Server may require dozens of component monitors to accurately assess its current status and performance.
Instead of creating component monitors one-by-one for every application server, you can assign a pre-made template. The template can either be one included with SolarWinds SAM, or a custom template you make yourself. For example, you can assign the included Microsoft Windows Server 2003-2008 template to your Windows 2003 and Windows 2008 computers and obtain vital statistics on all of them.
A template is only a blueprint and does not perform any monitoring on its own. Only after assigning the template to a server node are active assigned component monitors created.
To continue the car analogy, pretend you want to monitor a fleet of 50, 2010, blue Dodge Charger automobiles. Instead of defining the component monitors for 50 cars, you can define all the component monitors in a Dodge Charger template.
For a list of templates included in SAM, see the SAM Template Reference.
Assigned Component Monitors
Assigned component monitors are created by assigning Application Monitor templates to server nodes. Each actively monitors its assigned node according to its settings. Component monitors inherit these initial settings from the template. If you make a change to a template, that same change is rolled out to all assigned Application Monitors based on the template.
You can override the template settings at any time, breaking the inheritance relationship between the component monitor and its template. For example, the user name and password usually differ for each node, and you would select a different credential for each assigned Application Monitor, thus overriding the template setting for the Credentials field.
To restore the inheritance relationship between a component monitor and its template, click Inherit From Template next to the setting.
Continuing the car analogy, when you assign the Dodge Charger template to a Dodge Charger vehicle, you now have a set of assigned component monitors for monitoring the vehicle’s tire pressures, engine RPM, and so forth.
Assigned Application Monitors
An assigned Application Monitor runs its assigned component monitors at regular intervals, and then uses the status results from the component monitors to determine an overall status for the application.
If some of the component monitors are up and others are down, the Application Monitor follows the Status Rollup Mode setting in the Orion Web Console Settings to show either the worst status of the group or a warning status.
The difference between an assigned Application Monitor and a template is that the template is only a blueprint and does not perform any monitoring on its own. Only after assigning the template to a server node does SolarWinds SAM conduct any actual monitoring on the node.
To complete the car example, you assign the Dodge Charger template to all the Dodge Charger vehicles to create the assigned Application Monitor for determining the overall status for your Dodge Charger fleet. For example, the fleet may be 95% available at a given time due to warnings for some of the cars.
The following diagram illustrates the work flow involved in creating an application to be monitored by SAM.
To learn about FIPS-compliant component monitors, see FIPS support in SAM