Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

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

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