Announcing NCM 7.7With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more. See new features and improvements.

You can create a new template, copy a current template, or manage existing templates. You can access all templates through the All Settings > SAM Settings > Manage Templates page. This page includes all currently existing templates, assigned monitors, and thwack imports.

You may need to log in with an administrator account to perform these actions.

Create a template

You can create a template through the SAM Settings page or when managing templates. Creating a new template does not include any configured settings beyond the defaults for polling frequency and timeout (300).

Add general information and settings for the template including the name, description, tags, and polling frequency. Make

You have two options for adding component monitors. You can select Manually Add Component Monitors (select and add, editing in the template view) or Browse for Component Monitors (opens the Component Monitor Wizard). When added, you can modify the configurations and custom settings per monitor. For details on each monitor, you can access the help link.

When done, click Submit to save the changes.

Make sure the name of the template does not end in a space. If so, application resources may not list all applications. Edit the template name to remove any ending spaces in the name.

Create a custom template (Example)

The following procedure creates a SolarWinds SAM Application Monitor template that monitors a locally installed SQL Server instance. The template is simplified by using the Windows Service component monitors, a TCP port monitor for your SQL Server, and an HTTP monitor for the local Web Console.

Create an application template with the following component monitors:

TCP port component monitor to monitor port 1433, the port through which SolarWinds communicates with the SQL Server.

Service component monitors for the following windows services:

SolarWinds Alerting Engine

SolarWinds Network Performance Monitor

SolarWinds Job Engine

SolarWinds Job Scheduler

SolarWinds Module Engine

SolarWinds Syslog Service

SolarWinds Trap Service

HTTP component monitor to monitor port 80, the port through which you access the SolarWinds Web Console.

Create a SolarWinds Windows service application template

You can create templates specifically for the following SolarWinds Windows services:

SolarWinds Network Performance Monitor

SolarWinds Job Engine v2

SolarWinds Job Scheduler

SolarWinds Module Engine

SolarWinds Syslog Service

SolarWinds Trap Service

When creating the templates, use these instructions with variations based on the services you are monitoring:

Ensure the Port Number field corresponds to the port you use for the SolarWinds Web Console port, then click Submit.

Assign a template to a node

To begin monitoring with templates, you need to assign the application templates and monitors to a node. When assigned and enabled, the template collects and reports on polling data to the node according to the application monitors and configuration settings.

Edit a template

Every template, including default SAM templates, can be modified. You can change the name, description, general settings, and application monitors. You can also create a copy of a template and modify the copy.

Specify the values for the Polling Frequency and Polling Timeout fields.

Setting a polling frequency below 30 seconds can result in erratic monitor behavior.

To add a monitor, click Add Component Monitor. Expand and filter through the options to add one or more monitors to the template.

You can edit one or more monitors, update settings per monitor, and more. To review help information per monitor, use the help option in the web console.

When done, click Submit to save the changes.

Copy a template

You can modify current templates, or create a copy. With copies, you can use a base template from the default templates, imported templates, or templates you created. Using a copy for a new template can make the process much faster than starting a new template without pre-filled monitors and configurations.

The copied templates use the same name of the original name with "- Copy" appended.

If you want to completely modify a current template, use a copy to keep the original.

Select the application template you want to copy, and click Copy. A new template is added copying all of the application and component monitors, including any configured settings.

Export and import templates

Templates can be exported and imported to share and use between all Orion users. Exporting templates creates a file you can share on thwack with other users. Ensure the imported file format is XML with .apm-template extension. Unzip templates before importing.

Enter your THWACK account credentials when prompted. If you need an account, click Create Account and follow the steps. A message displays with the template exporting to THWACK. The template packages into an XML file with an extension .apm-template.

Click the Shared Templates on THWACK tab. A page opens and populates with available templates from THWACK.

Search or browse the templates. Select a template file and click Import. To view information per template from the authors, click the link for content exchange area on THWACK.

Enter your THWACK account credentials when prompted.

The template imports into the Orion Web Console. Search or browse to locate and edit the template as needed. If you import a template with the same name as one of your existing templates, the name of the imported template is modified by appending (n) to the name, where n is an integer.

If you receive an invalid file error, check the file format. The template should be XML code with .apm-template extension. If you are importing a ZIP, unzip the contents then import the template file.

Click Import Export > Import from File, and click Save. Browse and select the file with an extension .apm-template. The file must be XML. If you have a zip file, unzip all contents and select a specific file.

The template imports into the Orion Web Console. Search or browse to locate and edit the template as needed. If you import a template with the same name as one of your existing templates, the name of the imported template is modified by appending (n) to the name, where n is an integer.

Delete templates

Before you begin:

Deleting a template also deletes all of its assigned applications, both modified and unmodified.

To speed user interface interaction, data is not immediately removed from the database, but systematically updated every few minutes in the background.

Tag a template

Tags are descriptive labels that help you classify and sort your application templates on the Manage Application Monitor Templates page. The application templates included in SolarWinds SAM have already been tagged with several descriptive labels you can modify as you see fit.

Change between 32-bit and 64-bit polling

You should use 64-bit polling on 64-bit OS systems. Using AppInsight applications with 32-bit polling on 64-bit computers via an agent prevents certain performance counters from collecting information.

You may need to log in with an administrator account to perform these changes.