Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

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 MindTouch on Jun 23, 2016

Views: 14 Votes: 1 Revisions: 8

Overview

This article provides information about configuring alerts that target custom properties and why they do not evaluate NULL custom property values.
 

Environment

All versions of Orion products

Detail

 

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

 

For sample, 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"

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

 

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

 

More on this is found in the following article:

 

https://support.solarwinds.com/Succe..._value_is_NULL

 

 

 

 

Last modified
02:49, 23 Jun 2016

Tags

Classifications

Public