Understand the application/template relationship

In SAM, an application is a collection of component monitors inherited from a template when you assign the template to a node. A component monitor queries for values returned by a process, counter, status, or script. 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. SAM provides the following types of templates:

  • AppInsight templates are preconfigured application monitor templates that provide detailed information. If you have business-critical Active Directory, 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.
  • If you have other business-critical applications, apply one of the preconfigured templates included in 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 templates in THWACK.
  • If you have a proprietary 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, applications based on that template are affected. Conversely, if you make a change at the application level, only the individual application is 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 a template and that change will be inherited by the 100 applications based on that template.