Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > Handle custom properties with NULL and 'empty' values in alert conditions

Handle custom properties with NULL and 'empty' values in alert conditions

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,746 Votes: 1 Revisions: 8

Issue:

Due to the distinction in how SQL Server handles NULL and 'empty' values as table entries, alerts that are conditioned on custom property values must explicitly handle both the NULL and 'empty' value cases.

Resolution:

When building an alert condition that uses the value of a custom property, as follows:

  Trigger when any of the following apply:
  Custom_property is not equal to 'foo'

explicitly specify alert conditions to handle the distincition SQL Server makes between NULL and 'empty' entries, as follows:

  Trigger when any of the following apply:
  Custom_property is not equal to 'foo'   Custom_property is empty

This article applies to all SolarWinds Orion products using alerts and custom properties.

Last modified

Tags

Classifications

Public