Using Custom Properties sending Alert emails

Thanks for posting this Malik but the pictures do not work.

Thank you . Please check now.

If a node does not have this custom property set, and yet in the alert you use the ${email} custom property, along with, say, a standard e-mail address (someone@somewhere.com), will the fact that ${email} is empty cause an issue? We don't want our mailserver to be bouncing things around all day long if we can avoid it.

I.e., the alert will always go to someone@somewhere.com, but if ${email} is configured, it will also go there. Make sense?

Basically the Alert will check the column value if its empty for the node no email will be generated . However i dont understand the logic to have the nodes in the same email Alert as you are going to setup the specific Alert for the Support Group to receive an email . if you will mix all your Alerting with this single Alert it will be difficult for you to troubleshoot and finding which alert is triggered .

I will advise to have dedicated Alerts for the each custom group by name so you will know which alert you have to customize in the feature .

Basically, this is the idea:

on node A, all file system alerts go to SysAdmin

However, any file system that has the ${email} populated, will also go to ${email}

I.e., a DBA is not as concerned about /var as he is about /u11 filling up.

I would create a separate alert for my nodes having ${email} custom property and other nodes so not to mess up with single alert . 

otherwise if you will assign any email in the To section it will also considered to be generated .

Will the custom property accept multiple entries such as sysadmin@domain.com, foo@domain.com   ?

Yes you can have either multiple custom properties for each email domain / Or can have single custom property for different email domain .

The point here is whatever email you will enter under the custom property email alert will be sent to that email that is the main purpose of having such configuration . So you answer is YES .

I'm running NPM 11.5.2, and just tried to follow these steps in my own environment. I get the following error, indicating that the system is not accepting the variable:

The CP does exist, and it has at least one node with a value assigned to it. Has the functionality changed in the newer versions of NPM, or does database maintenance have to run between the creation of the CP/assignment of values and attempting to create the alert trigger?

You're using parenthesis when variables use curly brackets.

And if that still doesn't work try the full length variable that you can find from searching the variables within the body of the message.

${N=SwisEntity;M=Node.CustomProperties.YourPropertyName}