Customize Email Alerts | Teradata Viewpoint - How Can I Customize Email Alerts? - Teradata Viewpoint - Teradata Workload Management

Teradata® Viewpoint User Guide

Product
Teradata Viewpoint
Teradata Workload Management
Release Number
17.10
Published
February 2022
Language
English (United States)
Last Update
2022-06-28
dita:mapPath
lks1628075605455.ditamap
dita:ditavalPath
tky1501004671670.ditaval
dita:id
B035-2206
lifecycle
previous
Product Category
Analytical Ecosystem

This example describes how to customize the body of an email message used in an alert. You can define a threshold for a Teradata system metric when a specific event occurs. You can then specify that the event triggers an alert. The alert service has access to information on several properties of a monitored system, depending on the data collectors that you enable. If you configure the alert to send text, such as an email message, you can select which of the available properties to display in the message.

The following is an overview of the process:
  1. Configure the email delivery settings in the Alert Setup portlet.
  2. Create an action set in the Alert Setup portlet.
  3. Configure the Teradata system in the Monitored Systems portlet.
  4. Configure data collectors to monitor the configured Teradata system in the Monitored Systems portlet.
  5. Define alert rules in the Monitored Systems portlet.
  6. Review the alert messages that arrive in the email inbox.

Alert Property Syntax

The following guidelines apply to alert properties:
  • Enclose the alert property with curly brackets ({} ) and precede the expression with the dollar sign ($ ), as in ${alert_property}.

    For example, type ${databaseName} to return the name of the database that triggers an alert.

  • Make sure you enter alert properties with the correct case, because they are case-sensitive.
  • If an alert property is misspelled, uses incorrect case, or does not exist in the list of properties, the alert service displays the string literally.

    For example, if you use ${databaseNME} instead of ${databaseName} when adding the alert property, the alert service returns ${databaseNME} instead of displaying the name of the database that triggers the alert.