Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

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: 2,052 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