Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

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,731 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