Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

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

Alerts not triggering when custom property value is NULL

Overview

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

AND

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.

Environment

  • All Versions of Orion Platform

Resolution

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

AND

custom property value is not equal to 'X'

OR

custom property value is empty

Cause 

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

 

 

Last modified

Tags

Classifications

Public