Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.7 Administrator Guide > AppInsight for SQL > Edit the AppInsight for SQL template

Edit the AppInsight for SQL template

Updated July 27, 2018

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

You may need to log in with an administrator account to perform this action.

  1. In the Orion Web Console, click Settings > All Settings > SAM Settings > Manage Templates.
  2. Check the AppInsight for SQL template in the list and then click Edit.
  3. Edit component monitors, as necessary.
  4. Click Submit.

With administrator privileges, you can change the widgets (formerly called "resources") that appear on an AppInsight Details page. Each widget provides data configuration and display options, consuming data provided by the template application and component monitors. See Add resources and columns to views, and define subviews.

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

  1. Navigate to the AppInsight for Exchange 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 do so, navigate to the Node Details page, click Unmanage in the Application Details widget, and specify an interval for the assigned application monitor during which no statistics will be collected and no alerts will be triggered. 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 object 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  online IT community, THWACK, and read Tips & Tricks: Stop the Madness — Avoiding alerts but continuing to pull statistics.

Monitor with other SQL application 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 page, 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 SAM Component Monitor Types and SAM Template Reference. Refer to this THWACK article also, SQL Named Instance Monitoring.

 
Last modified

Tags

Classifications

Public