SAP ABAP Data Element ALSEVERITY (Alert: severity (alerts, monitoring type custom..))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CCM-MON (Application Component) Monitoring
⤷ SMOI (Package) CCMS: Monitoring Architecture
⤷ BC-CCM-MON (Application Component) Monitoring
⤷ SMOI (Package) CCMS: Monitoring Architecture
Basic Data
Data Element | ALSEVERITY |
Short Description | Alert: severity (alerts, monitoring type custom..) |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 11 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | severity |
Medium | 15 | severity |
Long | 20 | severity |
Heading | 0 |
Documentation
Definition
Severity is a measure of the importance of a monitoring attribute or of the component (monitoring object) to which an attribute belongs.
The severity is used to rank alerts that have the same importance. Among red alerts, the red alert that has the highest severity receives the highest ranking and is displayed in the alert monitor as the most important alert.
Severity is measured with a scale from 0 (not important) to 255 (very important).
Example: A monitoring attribute pertaining to the enqueue or update systems in the SAP system should have a high severity, as these are critical components. An attribute for "number of users on a server" should have a lower severity, as it is not as crucial to the continued operation of the system.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in |