Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
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: 195 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
22:03, 22 Jun 2016

Tags

Classifications

Public