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 > Server & Application Monitor (SAM) > 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: 46 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
09:48, 5 Oct 2017