Event Actions | Teradata Vantage - 17.00 - Event Actions - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

prodname
Advanced SQL Engine
Teradata Workload Management
vrm_release
17.00
created_date
June 2020
category
Administration
User Guide
featnum
B035-1197-170K

When you define an event, you also define what TASM should do if the event occurs. Note that TASM logs all detected events to DBC.TDWMEventHistory. TASM logs all detected events and performs notifications, regardless of whether an event causes a health condition or a change in the planned environment.

On the state matrix, Planned Environments describe the precedence of planned events. Period events, user-defined events, and event combinations (combinations of the previous two) activate a planned environment.

Health Conditions describe the severity of the system condition. System events, user-defined events (on the health condition axis), workload events, and event combinations (combinations of the previous types of events on the health condition axis) activate a health condition.

TASM changes to the state associated with the highest-precedent active Health Condition or Planned Environment.

The Always planned environment and the Normal health condition cannot have custom events triggers. These are the defaults with the lowest precedence and severity.

To define an event action, edit the state matrix directly or use Setup Wizard. On the Define and Map Unplanned Events screen, when you add to Available Events, you can choose from these actions to occur when the event starts and ends:

  • Post to QTable
  • Send Alert
  • Run Program