Documentation forServer & Application Monitor

Use SAM application monitor templates and application monitors

SAM includes over 250 out-of-the-box application monitor templates that you can assign to nodes to start tracking changes in your SAM environment immediately. Each template includes one or more component monitors comprised of code and scripts designed to monitor a server, application, database, or process represented by a node in the Orion Platform.

Need to get started quickly? Watch this video, and then assign a template to a node to create an individual application monitor on that node.

  1. Click Settings > All Settings > SAM Settings, and then click Manage Templates.
  2. On the Manage Application Monitor templates page, select a template and click Assign to Node.
  3. On the Create Assigned Application Monitor page, select a node and click Next.
  4. Provide credential details, and then test for component results.
  5. Click Assign Application Monitors.

You can customize and assign templates to individual nodes, or assign templates to groups of nodes automatically.

When you assign a template to a node, SAM creates an individual application monitor (also called an "application") for the node. When the next polling cycle occurs (every five minutes, by default), component monitors gather data and results appear in the Orion Web Console.

To display a list of application monitor templates included in SAM:

  1. Click Settings > All Settings.
  2. Under Product Specific Settings, click SAM Settings.
  3. Click Manage Templates to open the Manage Application Monitor Templates page.

Want to poll data from remote APIs? The API Poller feature also offers prebuilt templates.

Following are descriptions of terms related to application monitor templates.

Application monitor templates

An application monitor 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 prebuilt template to a node, which creates an individual application monitor specific to that node. The template can either be one included with SAM, or a custom template you make yourself. For example, you can assign the Active Directory 2016 Services and Counters template to domain controllers to begin monitoring services and counters immediately.

A template is only a blueprint and does not perform any monitoring on its own. Only after assigning the template to a node are active assigned component monitors created.

Some templates have specific port requirements, as detailed in the SAM Application Monitor Template Reference.

Check THWACK periodically for SAM application monitor template updates. Except for AppInsight templates, application monitor templates are not updated automatically during upgrades to avoid overwriting custom changes. For details, see Import and export SAM application monitor templates.

Component monitors

Component monitors are the building blocks of SAM. Each monitors the status and performance of a different aspect of an application. There are several types of component monitors, each containing settings that define what is monitored and how to monitor it. Some have prerequisites, configuration, and credentials requirements for target systems.

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%. Later, you can configure alerts to notify key staff if monitored values exceed set thresholds.

As an analogy, pretend 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.

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.

Click here for a list of available component monitors. Click here to learn more about thresholds.

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 change a component monitor in a template, that same change is made 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 (also called an "application") runs its 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 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 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 and determine 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 workflow involved in creating an application to be monitored by SAM.

AppInsight templates

AppInsight templates are specialized, complex SAM templates designed for in-depth monitoring of Microsoft Active Directory, Exchange, IIS, and SQL. In addition to monitoring virtually every aspect of these key business tools at the server level, you can drill down into the datastore layer for performance data. For details, see Monitor with AppInsight applications.

Many templates, application monitors, and component monitors can use Orion agents to collect data from target servers. See Monitor with Orion agents in SAM.

Learn more

See also:

Additional learning resources include: