Showing results for 
Search instead for 
Did you mean: 
Create Post

Using Custom Properties sending Alert emails

After receiving lots of queries i will try to explain in screen shots what steps needs to take if you wish to use custom properties logic to send email alerts to respective location / or team responsible for that node and group.

Basically when you have bunch of Nodes and you just wanted to send emails to the related department / Engineering Team only

Or You may have monitoring nodes for multiple customers where you would like to send emails to related customer for the nodes for that customer /

This post  can help in order to configure .

Step #1 Creating Custom Property

Start with Custom properties

Settings > manager custom properties.

Add Custom Properties




Leave it blank and Submit


Step #2 Assigning email to the nodes

Go to Settings Manage Nodes.

(Select multiple Node you wish to assign the email ) and click Edit Properties.

Now assign the email you wish to assign so all the alerts will be sent to respected email for these nodes .

And Submit to save changes.



Step #3 Using Custom property name under Alert Trigger Condition

Now in Alert use the custom property name to send the email for required email address for each node.

Select the Alert you wish to Edit and Edit Trigger Action > Send an email /page.

Add Trigger Action


When the alert will trigger it will use the email you have assigned to the Node.

***** Adding CC you can create more custom properties to include CC emails such as an example below ****






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 (, 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, 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,   ?

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.


Argh! That's a Homer Simspon moment for sure.... thanks muckman​! I need to get my eyes checked!

So i just tried to implement this at my site and by adding in the variable to the alert notification it ended up stopping all emails at my site for the alert

Looking at the events for Orion i see the following


So it looks like my system is not translating the variable into what is saved in the custom filed.

I tried using both ${email} and ${N=SwisEntity;} but both have the same issue.

I'm running on SolarWindsOrion Platform 2015.1.3, NPM 11.5.3, SAM 6.2.3 if that makes a difference.

Ok so i solved my own issue,

after reading the following post Using a Macro for email alerts in Advanced Alert Manager

i ended up having to alter the variable in the alert text from ${email} changed to ${}

Does this solution still work with NPM 12.0? I'm trying to implement it in our environment, but when modifying the default send email action, it will not accept my variable in the To: field, no matter the format I enter it.

In my case I found that the variables were case sensitive.  I just recently updated to 12.0 and my email alerts are still working.

This is exactly what I was looking for.  Thank you!

Hi Folks, there will be a class on 9/21/16 over custom properties with live Q&A. It will be recorded and posted in the Customer Portal for later viewing.

This works great for people that have large networks with multiple regional sites, and when they only want to be Alerted for a Node that is in their region. 

Something that I think is important to note and should be included in the article, is that you will need to adjust the variable if the Alert is for any other object besides Node.  For example, a SAM component Alert you would use: ${N=SwisEntity;M=Application.Node.CustomProperties.Email}.  Application monitors are considered "child objects" on Nodes.  Therefore, when a component triggers an Alert, Solarwinds will look to see which Email address you have assigned to the Node where that component is applied. 



Please let me know the variable used in recipient field to trigger alert on interfaces.



I don't have a chance to check it out for myself right now, but you can find it by clicking on the "Insert Variable" button in the Emaill Trigger Action Message section for that interface alert.  Search for that Email custom property that you created.  Then copy and paste that variable into the Email To: field.  If you can't find what I am referring to, please let me know, and I will get it for you next time i have a chance.

- Parker

While I can't speak for older versions -- as I'm utilizing NPM v12.1 now, this does indeed work for Groups currently. Works well I might add. For the lesser cared about environments I apply a custom property to the group and simply alert on the status of the group.

FYI GoldTipu​.

@sum_giais This is very valuable feedback i haven't tested this with V12 it might be added feature . Also i wasnt aware as i moved out from the NPM and Core to another product.


I will test that in the lab .

After I created a Custom Properties, and using Groups as it object type, the Custom Property does not seem to pass to Action as a variable. 

Screen Shot 2017-10-04 at 9.38.37 AM.png

As i said it wont work with the groups ... ONLY NODES -

Note - I cannot vouch for this functioning in versions lower than NPM v12.1.

Try this... ${N=SwisEntity;M=CustomProperties.GroupContactEmail}

My custom property that is applied to the groups is named g_contacts, so my variable I put in the 'To:' section is ${N=SwisEntity;M=CustomProperties.g_contacts}

I've been using this feature successfully on groups since NPM v12.1 (I'm currently on v12.2 and it's working.)

It's actually very easy to find - simply go to your message, and click insert variable, then search for it.


I have been using custom properties for email recipients for years, however now I cannot get it to accept more than one in the TO field. These are alerts and properties that have been working for years.  I just upgraded to NPM 12.2 and SAM 6.4 two days ago.


Not to revive an old thread this late on a Friday but I was able to get this to work for an alert on an Application Alert and not a node. By putting the following query into the Recipients To field:


email_to being the name of the custom property and then using the ApplicationID to find it in the where clause.

This may be posted elsewhere but I stumbled upon this when I had a reason to do this for an application.

You can actually simplify this by just using the custom property direct name. Not sure it really makes a difference but I've tested this in my NPM 12.3 environment and it works great.${N=SwisEntity;M=Application.CustomProperties.EmailTo}

One note (and I will open a case on this) after three days, this quit working for some reason. It started substituting the literal string into the TO field instead of addressing it as a variable.

I may have run into the same issue recently and am contemplating opening a case next week. Perchance do you have a second email address included as a recipient?  What I have found is if the variable is listed by itself, it resolves correctly.  But if I add a second recipient, the variable get placed between two pairs of curly braces instead of one pair and therefore resolves to the literal string.  This happened after upgrading to NPM 12.3 (from 12.2) and Orion 2018.2 HF6 (from 2017.3) about two weeks ago.

Custom Properties.JPG

I don't find email column to enter an address.

Hey benyin​, You have to create a new custom property field. This can be done from the all settings page.


slinton​, You nailed it. I'm seeing the exact same behavior as I look closer. I also tried adding a second custom properties and it is doing the same thing with adding extra curly braces to both variable. When I remove everything else and only have the single variable, the alert works correctly and pulls the correct contacts from the custom field. I've opened a case on it and will update this thread once I hear back.


I opened "Case # - 00207229 Custom Properties variable (new format) used as recipeint in "send an email/page" trigger action of an alert resolves to literal when additional email address is specified".

I received two responses from Solarwinds:

1)  Your issue is actually a bug that was resolved in a future version of SAM. Please upgrade SAM to 6.7 resolve your issue. This will also install the new version of Core, which is 2018.4. Your currently installed products should be compatible with this version, otherwise they will be automatically updated with SAM.

Followed a few minutes later with:

2)  My apologies, upon checking again, it looks like you will need to wait until NPM 12.4 is released before the issue will be resolved. Currently 12.4 is in RC, but it should be released to the general public soon. Please note that upgrading appears to be the only resolution for this issue.

I responded and asked why there is no HF for this since there was in Orion 2017.3 when this problem previously occurred and am waiting to hear back from them.  More than likely, we are stuck with a loss of functionality

The issue i was reporting is i don't see any email field to enter an address in the custom properties when adding nodes.

Can some help me with step by step procedure to create an alert for my nodes.

Custom Properties 1.JPGCustom Properties.JPG

You firstly need to create a custom property name Email only then it will be listed here.

  • Click Settings > All Settings, and in the Node & Group Management grouping, click Manage Custom Properties.
  • Click Add Custom Property.
  • Select an object type, and click Next.
  • Provide the required information, and click Next.
  • Select Restrict Values, add values for the property, and click Next.
  • Click Select Nodes.

    Once done it will be listed here .

Thank you.

​Can you please explain the Restrict values when creating a Custom Property.

​What is add value.


Chris Benyin

IT Officer

1 Kofi Annan Street, Airport Residential Area

PMB CT 470, Accra

​T:233 302 770 522 . M: 0579055589 . F:233 302770499

That's weird. So, you're seeing the $variable name instead of the data that is contained within the CP for that node/element?

Correct. It looks like this as soon as any other email addresses or variables are added. Here is an example that shows the setup within the to field and then the second screenshot is the results.


Format the recipient like this.


no spaces, and put in your own commas.  when you save it and go back to it, it is split correctly without the added {{{{

then every time you edit it, you have to remove all of them and reenter all of them with the commas and no spaces.

I am in the process of setting this up but my variable is wrong so the alert will not go out.  I tried ${email} and ${N=SwisEntity;} and still no email goes out. What am I missing? 


Thank you for posting this.  I have been setting up Node Custom Property alerting and this post helped me figure out what the Custom Property I was looking for.  I found it via the database manager and your tip above helped me figure out the rest.  Thank you!!!

We call our custom properly: DiskUsage_Email

We reference this in the 'to' section (after a known/valid e-mail, just so

in the event that there is no DiskUsage_Email for the particular device, it

will still go out):


for nodes we have Node_Alert_Email, and similarly


If you go to the body of the e-mail, you will see a button for 'Insert

Variable' Use this to find your custom property, insert it, then copy it

and paste it in the To: field. That's how we got it to work.

Note that my variables do not have the 'Node.' prefix as yours does. The

custom properties are simply in the main bucket of SwisEntity


On Mon, Aug 26, 2019 at 3:44 PM martian monster <

Yup the variables will certainly change (as I'm sure we all have our own use case.) Much of it depends on your reference point (your alert) and what type of entity you're alerting on (group, node, application, volume etc..) Some examples..

Custom property applied to group, alerting on group: ${N=SwisEntity;M=CustomProperties.Group_Contact}

Custom property applied to node, alerting on node: ${N=SwisEntity;M=CustomProperties.Email_Contact}

Custom property applied to node, alerting on interface: ${N=SwisEntity;M=Node.CustomProperties.Email_Contact}

Custom property applied to node, alerting on hardware component: ${N=SwisEntity;M=HardwareInfo.Node.CustomProperties.Email_Contact}

Custom property applied to storage array, alerting on hardware component: ${N=SwisEntity;M=HardwareCategoryStatus.HardwareInfo.StorageArray.CustomProperties.Storage_Contact}

Version history
Revision #:
1 of 1
Last update:
‎05-10-2015 03:57 AM
Updated by: