Documentation forServer & Application Monitor

Edit the AppInsight for SQL template

The AppInsight for SQL template includes numerous component monitors to provide data about monitored SQL instances. If you modify these settings and configurations in the template, the details in AppInsight application monitors already assigned to instances update to match.

The primary reason to edit most SAM templates is to set general configurations such as polling frequency, polling method, and thresholds for warning and critical states for monitored metrics before assigning templates to nodes. The AppInsight for SQL template includes several component monitors with default settings that cannot be modified due to dependencies. Also, you cannot add component monitors to this template.

To monitor specific instances without using AppInsight for SQL, SolarWinds recommends Monitor with other SQL application monitor templates.

See the SAM Template Reference for a list of component monitors included in this AppInsight template. You can also select the template on the Manage Application Monitor Templates page and click Edit to display component monitor details, and then make any necessary changes.

You may need to log in with an administrator account to edit templates.

To begin gathering metrics, assign the template to a SQL instance.

Customize AppInsight for SQL monitoring

In addition to editing the AppInsight for SQL template, there are many ways to customize AppInsight for SQL monitoring, as described here.

Customize widgets on the AppInsight for SQL Details page

With administrator privileges, you can change the widgets that appear on an AppInsight for SQL Details page. Each widget provides data configuration and display options, consuming data provided by the template application and component monitors. Click here for details.

Set custom properties for a node

You can also set custom properties for the AppInsight for SQL application monitor assigned to a specific node.

  1. Navigate to the AppInsight for SQL Details page for a node.
  2. Click Edit Application Monitor in the upper right-hand corner of the page.
  3. Edit the Application Monitor as necessary and click Select resources as needed, then click Submit.

Consider adding the node ID in the Application Monitor Name field so you can easily identify this monitor later.

Remove a database from an active AppInsight for SQL node

If you need to remove a database from an active AppInsight for SQL node, one way to do it is to "unmanage" the node to halt polling and related alerts. To do so, navigate to the Node Details view, click Unmanage in the Application Details widget, and specify an interval for the assigned application monitor during which no statistics will be collected. For another workaround, see Hide Databases from Appinsight for SQL via the All Databases widget.

When a database, node, or interface is "Unmanaged" in SAM, the element is not polled and alerts are not triggered because the alert engine does not detect any change on the object. However, if you create a new alert or edit conditions for an existing alert for an unmanaged database/node/interface, the alert will be triggered and alert actions will occur because the Orion Platform does not check to see if the element is unmanaged before running the alert, by design.

To learn about continuing to gather statistics about a database, node, or interface while blocking a flood of alerts, visit the SolarWinds online IT community, THWACK, and read Tips & Tricks: Stop the Madness — Avoiding alerts but continuing to pull statistics.

Monitor with other SQL application monitor templates

To monitor specific nodes without using AppInsight for SQL, SolarWinds recommends using SQL templates. For example, you may have a large amount of SQL database instances to monitor such as a service provider with SQL instances per customer. To avoid performance issues, you may not want an AppInsight for SQL running for each of these instances.

To monitor a SQL named instance, first add it as a standard node by navigating to the Manage Nodes view, clicking Add Node, and providing required details.

Do not select the option for AppInsight for SQL for the node yet — you can apply a SQL Server template on the Manage Templates page, as described next.

After adding the SQL named instance as a standard node, follow these steps to assign a SQL Server template to the node.

  1. Click Settings > All Settings > SAM Settings > Manage Templates.
  2. Search or browse for SQL Server templates.
  3. Select the SQL Server template you want to assign to SQL named instances to monitor. You may want to assign multiple templates to the node. Assign these one at a time.
  4. Once assigned, you can edit one or more templates by checking the boxes and selecting MultiEdit.
  5. Enter the SQL named instance for the SQL Server Instance.
  6. You can further modify the templates and application monitors as needed. Data captured through the templates should display on the Node Details for those monitored nodes.

All component or application monitors in a template relate to the SQL named instance, not the server. In Microsoft, the SQL server is a series of instances. These instances are default, unnamed instances or specifically named SQL instances. An instance is an installed Microsoft SQL in a specific directory path.

For a list of available templates, see the SAM Template Reference. See also SQL Named Instance Monitoring.