Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Custom Properties with values of NULL are not evaluated in Alerts

Custom Properties with values of NULL are not evaluated in Alerts

Table of contents
Created by Riggs Clough, last modified by Laura C on Oct 05, 2017

Views: 960 Votes: 1 Revisions: 12

Updated October 5, 2017


This article provides information about configuring alerts that target custom properties and why they do not evaluate NULL custom property values.  When objects are discovered through the node discovery process, the custom property fields are NULL, until a value is set for them.


All versions of Orion products



You need to verify that every node has a value assigned to the Custom Property in question. If a value is left NULL, the alert does not evaluate it as part of the condition.


For example, if you set an alert to have the following custom property condition:

Node - ServerGroup - is not equal to - "production"

  • This would trigger on a custom property value for ServerGroup of "dev"

  • This would not trigger on a custom property value that is left as a NULL value


The workaround is to add another Condition for "Node {custom property} is empty".


More information on this workaround is found in the following article:





Last modified