Alerting different groups about downed components

Have you considered using custom properties instead? You can even create a custom property called "NotificationTeam" that is simply the email address of who should be notified. You can then use this custom property to dynamically populate the email address "To" or "CC" fields in the email alert action so the message is routed to the appropriate individual dynamically depending on who is responsible for the system or application. You can use either Node or Application Custom Properties for this purpose.

I like the idea, but I'm having trouble getting the variable to translate in the "To:" field.

My custom property is on "Applications" and the "Property Name" is NotificationTeam.

Shouldn't my variable then be: ${Application.NotificationTeam}

Hi Jason,

I have recently been dealing with the same challenge, which is well described and answered here: How do you reference an application custom property in an alert.

Depending on the version of your SAM you either need a workaround as per the above thread, or you just need latest SAM 6.1 where ${APM_ApplicationCustomProperties.MyProperty} should work just fine

I'm on 6.1 but I'm still just getting the variable back in both the To field and message body. Let me post a picture of my application custom property, maybe I'm missing something obvious.

Here is my variable:

${APM_ApplicationCustomProperties.NotificationTeam}

***Update***

I got it working, but not using the variable above. Instead I used the SQL query from your other suggestion. However, I did not have to add the ":" in the custom properties as stated in the article. I just placed the following line right in to the "To:" field. Perhaps this is what was fixed in 6.1?

${SQL:Select yourcustomproperty FROM APM_ApplicationCustomProperties WHERE ApplicationID = ${ApplicationID}}

Nice one, well done I will need to adjust my alerts to accommodate 6.1 fix as well. I have upgraded yesterday, didn't try yet but thought that I will be ok with ${APM_ApplicationCustomProperties.MyProperty} only.

Correct. This was resolved in SAM 6.1 such that the custom property alone can now be used without any SQL trickery.

I couldn't get ${APM_ApplicationCustomProperties.MyProperty} to work so let me know if works for you. I still had to use the SQL query, but I was able to do so without the ":" trick that was required previously.

Hi aLTeReGo,

Would you be able to provide the correct syntax for this macro. Both me and jason1320 could not get it to work

In the example above the macro ${APM_ApplicationCustomProperties.NotificationTeam} should work provided you are running SAM 6.1. SAM 6.0, 6.0.1, and 6.0.2 however must continue to use the workaround listed above. If this macro is not working for you in SAM 6.1, please open a case with support so we can troubleshoot the issue properly.