For Advanced Alerts I would like to have different Trigger Actions based on Variables not specified in the Trigger Conditions

KwameB

Is it possible to have different Trigger Actions based on Variables not specified in the Trigger Conditions?

This is an example of what I would like to achieve:

Have 1 main alert for "Node Status" (This would monitor all nodes despite any custom properties or anything else used to differentiate the devices)

The trigger condition would be "Node Status is equal to Down"

The trigger action would be an e-mail with a message saying something like"

"${Support_Team} Node Status Alert: ${NodeName}'s Operational Status is: ${Status}" (Where support team is a custom property with a value of either TEAM_A, TEAM_B or TEAM_C)

So when a node is identified as down by the Trigger Condition the Trigger Action would then in turn see the custom property value of {Support_Team} being TEAM_A, & an e-mail is sent to an e-mail address associated with TEAM_A, & if the value is TEAM_B, an e-mail is sent to an address associated with TEAM_B instead.

Currently the only way I can see how to achieve different Teams being notified for only devices which they offer support for is to create separate alerts with basically the same Trigger Conditions with the only difference being (in my case) "${Support_Team} is equal to TEAM_A" or TEAM_C etc. each with different Trigger Actions with e-mail addresses to match the {Support_Team} value used in the Trigger Condition.

Is this currently possible?

I am trying to avoid creating duplicate alerts for each team with basically the same Trigger Conditions.

mcbridea

I think I follow what you want to do. If a node belonging to  support group A goes down notify group A and so on for B and C.  You can do this by creating yes/no custom properties called Support A, Support B..., then tag all of the devices with the appriopriate support group. From there create the alert Status equal to down AND Custom Property Support Group A equal to Yes. Set the action to alert Gouup A. Save that alert and then copy it and modify for the other custom properties and groups.

I know it's not nearly as slick as being able to do it on one alert with variables but it is what we have at this point.