Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

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

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

Created by Interspire Import, last modified by Brian O'Donovan on Nov 28, 2018

Views: 1,979 Votes: 2 Revisions: 10

Updated: November 28th 2018

Overview:

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.

Environment:

All versions of Orion

Cause:

This is due to how SQL handles empty & NULL values.

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 distinction SQL Server makes between NULL and 'empty' entries, as follows:

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

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

Last modified

Tags

Classifications

Public