Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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,850 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