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) > 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: 151 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
22:24, 22 Jun 2016

Tags

Classifications

Public