Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Alerts not triggering when custom property value is NULL

Alerts not triggering when custom property value is NULL


When alerts are configured to trigger on custom property values, they fail to trigger when value is NULL

For example:

Trigger alert when node is down


Custom property value is not equal to 'X'


In this case, if a node is down and the custom property value is NULL, it will not trigger the alert.


  • All Versions of Orion Platform


In the SQL Server, NULL values are not treated in the same way as 0. An alert that is configured to trigger on a designated value returned by a custom property may not trigger as expected if the custom property returns NULL.

You must set the alert to also be triggered if the custom proper value is empty.

Note: A custom property returns NULL if there is no value assigned to it in the SolarWinds database. 

The example given above must be changed to: 

Trigger alert when node is down


custom property value is not equal to 'X'


custom property value is empty


Failure to trigger alerts happen when a custom property is undefined and returns NULL.



Last modified