
Hey everyone,
I was wondering if we can do the following:
We would like for an Advanced Alert within NPM to email a different email address, depending on a node's group membership when it goes down.
So, for example, if a core switch in New York goes down, the alert is sent to NetAdmins-NY@domain.com; conversely, if a core switch goes down in Miami, the alert is sent to NetAdmins-MIA@domain.com.
Does that make sense? One alert defined, but many different email actions available, based on group node membership, within that alert.
Please let me know. Thank you!
Anyone?
Hi ET,
Yes, this is indeed what we understand. The problem is, we can't figure out a way to send alerts to different email addresses depending on the Location, defined as a trigger condition.
So in other words, the trigger condition might look like this, logically:
IF Location=Miami
THEN email networkadmins-miami@domain.com
IF Location=NewYork
THEN email networkadmins-newyork@domain.com
Does that make sense? We wish to have all of these defined inside one alert itself -- and so that we can avoid creating alerts for each email recipient group.
Thank you for your help.
Well, there's not exactly this functionality inside single alert definition :(
But you can specify variable inside mail TO which is evaluated for each node. If each your node has correct information filled, it's done automatically.
This will evaluate property Contact on node where alert occurred.
Or You can of course create VBS (or run external program) where you add own logic and send email via CDO or other engine.
Hmm... this may in fact do what we are looking for. Thank you for the help, we will test and see.
Thank you again!
of course you can use any property, ${Contact} was only example. You can create own property if you need.
ET's solution is what we use. Each node has 2 Custom Property fields that contain email addresses: "AdminEmail" and "AppAdminEmail"
These fields are populated with the email addresses for the administrators of the node and (if necessary) the hosted applications. It is much easier to manage custom properties over multiple nodes than it is to deal with multiple alert templates.