configure email alerts for events

Email Notifier Adapter

The Email Notifier Adapter sends email, based on notifications, to a designated list of users using an SMTP server.

Look at the document called SAM_92_Notification Adapters_User_Guide.pdf in the SAM portfolio

BRENT

you can use ACT_Mail from the backend.

dmctl -s invoke ACT_Mail::ACT-Mail sendmail

if you have the mail server configured on the ACT_Mail configuration.

[root@sp099s8000 ~]# sm_service show --cmdline 8000-MAILER
sm_service install --force  --unmanaged  --startmode=runonce \
'--name=8000-MAILER' \
'--description=EMC SMARTS sendmail Adapter' \
'/opt/InCharge8/SAM/smarts/bin/sm_notify' \
'--output=Mailer_Smarts' \
'--server=8000-SAM01' \
'--confdir=/opt/InCharge8/SAM/smarts/local/conf/notifier' \
'--conf=mail-notify.conf''

To decide whether to send selected alerts (instead of "all"), simply go into SAM and create a notification list that filters out everything except what you want.  Remember to use the SAM notification console to "test" your filter criteria first to see which alerts they "reveal" before replicating those filter settings to a notification list.

Then in the mail-notify.conf file, specify the name of the Notification list in this section  ("Default" gets everything):

              # NL subscription.
              #
              GA_NLSubscription::mail-Default-NL-Subscriptions
              {
                       NLName = "Default"
              }

Using that mail adapter is not a very elegant way to send to multiple email queues.  I.E. if you want to send network element alerts to the network team, server alerts to the server team, etc.  you would have to spin up a new instance of the mail adapter for each email list.

A better way to do it is to use the script Adapter, and call a sendmail script.  In that script you could use case statements to select the recipients based on the "ic-Classname" "ic-DisplayName" etc.  Of course that is a significant amount of development effort, so you might elect to use a few mail notifiers (say 5 or less) to get you "phase I" mail functionality, until you have time to get the script-notifier to work the way you want it.

Like they say in the Notification Adapters user guide, the mailer does not send "clears" by default, and I do NOT recommend sending emails for anything other than "Down" on critically important devices, otherwise the volume of emails received by your users will create a revolt and they will want to find you with a rope to tie you up and beat up on you.

As you learn to refine/define critical components (Array failure / critical "Application" failures / "hard drive" failures, etc and send emails on them to only the correct email distribution list(s), then you can widen the scope of what you send.

It will take you a week or two to get Phase I working, and probably 6 months of trial and error on the script adapter (Phase II) version before you are satisfied with it.  After that you will only need minor tweaks on the case statements as new classes are released in new SMARTS versions/patches.

Hi vtrack,

You can use notification adapter, but personally, I would set up a server tool and use escalation policy to send emails.In escalation policy, you can control the notifications by setting up filters, for example: source=INCHARGE-AM-PM

If you are using linux, you can create a shell script to call postfix or sendmail and take certain attributes from your notification.

You can check some server/client tool examples in /opt/InCharge/SAM/smarts/actions/server or /client

you can follow the Smarts document to create your escalation policies.

Hope this helps.