Alert Details

Teradata Server Management Web Services User Guide

brand
Hardware
Software
prodname
Server Management
vrm_release
12.07
category
User Guide
featnum
B035-5350-097K
Data Field Description
Time Stamp Indicates the time and date the alert was detected.
Time Received Indicates the time the alert was recorded by Server Management.
Severity Specifies one of the severity levels of the alert that is being reported to indicate the level of impact to the component:
  • OK
  • Information
  • Warning
  • Degraded
  • Critical
  • Fatal
Sequence Identifies the sequence in which the alert was recorded.
GUID Specifies the unique global identifier assigned to the alert.
Status Indicates the status of the alert.
System Name Specifies the name of the system where the alert was detected.
Managed Element Identifies the component ID for which the alert was detected. This is also known as the unique name assigned to the component.
Managed Element Alias Identifies the default alias of the component.
Sub Type Indicates an optional alert type, depending on the Reporter Type or type of managed object. Some examples include:
  • MP-RAS nodes: PostError, AssetChange, SettingChange, StreamsError, and ConsoleLog
  • Linux nodes: Syslog
Subsystem Identifies one of the following subsystems where the alert originated:
  • Client
  • Database
  • Network
  • Node
  • OS
  • Power
  • ServerMgmt
  • Storage
  • Other
Domain The source from which the alert originated in conjunction with Message ID, uniquely identifying the type of alert.
Message ID Specifies an alert name, message key, or number unique within the Domain for a specific alert type. For example, NodeAgent-AutoCheckSMNodePkgVersion.
Reporter Type Identifies one of the following categories to which the alert belongs:
MPP_Alert
Indicates an alert condition which is processed by the Alert Manager.
PSR_SummaryAlert
An alert that reports on a group of alerts. A problem alert summary.
TVI Disposition Specifies one of the following TVI Disposition statuses:
  • None: No disposition determined.
  • Ignore_Maintenance: The maintenance window was open when this alert occurred. Alerts for components in a maintenance window are marked Ignore_Maintenance. A summary alert is still escalated while in a maintenance window; however, the maintenance flag is on, so no incident is created at the backend.
  • Ignored: Not escalated by TVI, because it has been specifically excluded by the rules.
  • Abeyed: Summary alert not escalated by TVI because a previous similar alert was escalated and subsequent escalation is suppressed for a period of time.
  • Escalated: Summary alert has been sent out to the TVI backend to be considered for incident create or update.
Repeat Count Indicates the number of times this alert has repeated since the value in Repeat Start Time.
Repeat Start Time Specifies the time a repeat of this alert was first seen within a day.
Description Specifies the message that describes the alert that occurred.
More Information Contains properties specific to the alert being reported, including operating system, computer name, and log message.