Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Custom SQL Alert best practices

Custom SQL Alert best practices

Table of contents
Created by William Muhle, last modified by MindTouch on Jun 23, 2016

Views: 1,863 Votes: 0 Revisions: 5

Overview

This article provides information about the  best practices to use when creating a custom SQL alert.

Environment

Orion platform, all versions

Detail

  • If you are using a custom SQL query in the alert definitions, make sure that the trigger and the reset conditions are as specific as possible. The less data they return, the better. Reset conditions are usually more prone to return too much data.
  • It is far better to make two very specific alerts than one broad scope alert.
  • Make sure that your custom SQL queries do not return more than a few thousand records. If the query does return to many records, it can result in the query causing slowness for the rest of the application, and it can also cause failures on the alert/reset.

 

 

Last modified

Tags

Classifications

Public