Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Server & Application Monitor (SAM) > Server & Application Monitor Getting Started Guide > Monitor > The relationship between applications and templates

The relationship between applications and templates

Table of contents
No headers
Created by Chris.Moyer, last modified by Anthony.Rinaldi on Aug 23, 2016

Views: 1 Votes: 0 Revisions: 6

In SolarWinds SAM, an application is a collection of component monitors inherited from a template. A component monitor queries for values returned by a process, counter, status, or script. SolarWinds SAM uses the data received to display vital statistics concerning the health of the system.

Templates provide blueprints for the applications to be monitored. You can customize templates, and use only the component monitors you need to monitor a specific environment. SolarWinds SAM provides the following types of templates:

  • AppInsight application templates are preconfigured templates that provide detailed information. If you have business-critical Exchange, Microsoft IIS, or Microsoft SQL instances, use the AppInsight templates to monitor these applications. These templates have their own mechanism of discovering elements of an application dynamically. They also have special licensing.
  • If you have other business-critical applications, apply one of the many preconfigured application templates that ship with SolarWinds SAM. SolarWinds recommends deploying a single template, making necessary edits to customize it to your environment, and then deploying the edited template on all similar applications. You can also obtain a template from the thwack community for an application not shipped with SAM.
  • If you have a custom, homegrown application that you need to monitor, you can build a custom template.

The following illustration explains the template and application relationship. If you make a change at the template level, the applications based on that template will be affected. Conversely, if you make a change at the application level, only the individual application will be affected.

This inheritance relationship is beneficial if you need to make a lot of changes. For example, rather than making one change to 100 applications (and therefore 100 changes), you can change one item that will affect all 100 applications based on that template.

File:Success_Center/New_Articles/SAM-CHM-Import/Onboarding-Guide-CHM-SAM/040/010/03000002_422x387.png

 
Last modified
15:41, 23 Aug 2016

Tags

Classifications

Public