Adding and Copying Alerts - Server Management

You can create alerts for a single site ID or all site IDs and select alert actions from the configured action sets in the Alert Setup portlet. You can create different alerts to monitor different conditions for each site ID depending on the purpose of the site ID, such as production, development, and so on. If you want alerts to monitor the same conditions on any of the site IDs, you can create alerts for all sites.

From the Viewpoint portal page, select .
Open the Server Management portlet.
From the Configure list, click Alerts.
From the SiteIDs list, do one of the following:
- Click All for alerts on all sites.
- Click a site ID for alerts on a single site.
From the Alerts list, do one of the following:
- Select to add an alert.
- Select in the row of the alert you want to copy.
- Select the name of the alert you want to edit.
Enter a name for the alert.
[Optional] Select the Enabled check box to enable the alert.
Under Alert Rules, do the following:
1. Select the scope of the alert rule using the Match list.
  - All requires all criteria match to trigger the alert.
  - Any requires any one criterion match to trigger the alert.
2. Select a metric from the list and enter a threshold value.
3. [Optional] Add or remove rules.
4. [Optional] Select the Notify again if alert updates check box to be notified if the alert is updated.
Under Alert Action, do the following:
1. Select an alert action from the Action list.
2. Type a limit for Do not run twice in ... minutes.
  The alert action does not run more than once during the time span you entered.

[Optional] Under Message, enter a message that appears when the alert action executes.

Message can use the following parameters to provide details about alerts that would otherwise not be seen directly with an SNMP trap:

Metric	Description	Property Name
CMIC Version	CMIC version that forwarded the alert	${cmicversion}
Description	Message describing what occurred, including a recommendation	${description}
Domain	Source where the alert originated and, in conjunction with MessageID, uniquely identifies the type of alert	${domain}
ID	Unique global identifier (GUID) assigned to the alert	${id}
Impact	Description of the alert cause.	${impact}
MessageID	ID identifying the rule that processed this alert and describes the category of this alert	${messageid}
ReportingAlias	Identifies the Server Management alias of the component failing or reporting the problem	${reportingalias}
Scope	Describes the number of alert and component types involved in the alert scenario. Alert type is defined as a unique alert Domain/MessageID.	${scope}
Severity	Severity level of the alert group	${severity}
SiteID	Teradata system that generated the alert	${siteid}
Subsystem	Subsystem where the alert originated	${subsystem}
Status	Status of the alert	${status}
Synopsis	Description of the failure which may include the meaning and recommendation	${synopsis}
System	System name from the Summary Alert, if applicable	${systemname}
Time	Time and date the alert was detected	${time}
Type	Summary or alert type	${type}

Click Apply.
If the operation is successful, appears. If the operation fails, appears. Verify the settings are correct and try again.