This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

send an alert email to a group based on a node variable

imcguinness over 6 years ago

Hi,

I have been searching but can't find a thread that matches so sorry if this has been asked before.

Also, if i have posted this in the wrong area, let me know.

I would like to be able to make 1 alert for a system/service that sends the alert email to a different group based on a node custom variable.

e.g. if i had 2 SQL servers, 1 for development and 1 for production and they had a node variable where i selected one or the other from a drop down list.

Basically I'd like to set up 1 alert that said If the node goes down and the node.server_type = development email to dev_team@xyz.com, if node.server_type = production email to alerts_group@xyz.com.

Then another alert that said if the SQL application goes down and the node.server_type = development email to sql_dev_team@xyz.com, if node.server_type = production email to sql_alerts_group@xyz.com.

If possible i'd like to store those email addresses as a variable somewhere and also allow for multiple addresses in the variable. e.g. production email to alerts_group@xyz.com, it_team@xyz.com

I just cant get my head around the best way to store the lists (one variable with many entries or several variables with different names) and then picking the correct list in the alert.

Any and all advice and tips gratefully accepted.

Thanks

Ian

0 ebradford over 6 years ago

Hi Ian, I can think of 2 ways to do this. Neither seem ideal, but maybe these ideas will spark something for you.
1. Instead of having Solarwinds send the e-mail, pass the variables you need to an external program, then the external program can do the per-variable addressing.
2. Create a different alert, nearly the same, for each e-mail destination. Put the e-mail destination as part of the alert criteria too. But, this could quickly become unmanageable if you have a lot of e-mail addresses.
Just curious... have you tried putting a {Node.CustomVariable}@company.com type of entry in the address field?
Cancel
Vote Up 0 Vote Down

Cancel
0 po_malley over 5 years ago in reply to ebradford

Howdy ebradford,
Thank you! I used your last idea and it worked with the addition of a $. ${Node.CustomVariable}@company.com
Thank you again,
Pat
Cancel
Vote Up 0 Vote Down

Cancel
0 Seashore over 5 years ago in reply to po_malley

Hi
Another solution is to use a SQL variable. Below checks if it dev or prod and alters the email address to what you like.
${SQL:SELECT CASE WHEN NCP.Server_Type = 'Production' THEN 'prodteam@company.com' WHEN NCP.Server_Type='Dev' THEN 'devteam@company.com' NCP.Email_to END from NodesCustomProperties NCP where NCP.nodeid=${Nodeid}}
For the application alert you might need to change the Orion varieble in the end, ${NodeID}.
Otherwise just use above in the to-field.
Cancel
Vote Up 0 Vote Down

Cancel
0 ebradford over 5 years ago in reply to Seashore

Seashore-- I like it!
I hadn't thought of putting in a concise CASE statement in an address field. I suppose the CASE statement could even be put in a custom property, so for a common group of nodes, you could one CASE statement, and for another group, you could have different CASE.
Cancel
Vote Up 0 Vote Down

Cancel
0 Seashore over 5 years ago in reply to ebradford

Yes, using SQL variables you can use a lot of magic :-)
Cancel
Vote Up 0 Vote Down

Cancel