EJM Alert Template

From Address

List of all From addresses (to be unique within EAS).

To Address

eaglecsi@eagleaccess.com Target email address where email alerts should be sent.  NOTE: This will not work until we provision it within EAS and add it in ServiceNow.

Additional email addresses (DEV/Test) will be provided, if requested.

Alert_System

Alert System Identifier – Issued by EA Engineering Team.

Alert_Name

Alert Identifier (for possible further steps in ServiceNow, such as  File_Alert vs. DB_Connectivity) to identify all the different email alerts where different actions need to be taken.

Alert Program Name/Details

Program name, and where it is hosted, that is generating the alerts.

Email Format

Definition of the Email content (such as identification of fields required by ServiceNow Forms) on a per alert basis. Need to provide samples of all email alert types.
For example, PROBLEM WITH [Prod|Test] Environment -- GatherTableStats.sh on [Box Name] for [sid].

NOTE: Any future changes to the email format need to be coordinated with EA Engineering team.

ServiceNow Required Fields

Urgency, Impact, Category, Sub-Category - These attributes define the priority of a letter and to whom it should be addressed.

Custom Attributes

Specific to your Alerting System, for example, FTP User, FTP Filename, etc.

Email Alert Examples

Include examples of email alerts.

ServiceNow Processing Rules

Need to identify/define what/how the alerts are processed within ServiceNow.

NOTE: EA Engineering Team will work with you to define these rules.

Comments

1. Notify EAS team about any alert changes or new alerts created.
2. Keep eaglecsi@eagleaccess.com or eaglecsi@eagleinvsys.com email address as the first address in the Sender list.