The severity level of the log record. 'critical' is the highest severity level, followed in decreasing order by 'major', 'minor', 'warning', and 'normal', which is the lowest severity level. These severity levels can be further qualified with an indication that the 'health' of the system is effected because of this event. In such a case, these events are indicated with the '-health' suffix ( 'critical-health', 'major-health', 'minor-health', 'warning-health', 'normal-health'). Additionally, a health effecting event can be normalized by an associated event. For example, on the Network Management Unit, or NMU, the radio PPP link going down is normalized by the radio PPP going up, and vice versa. When a health effecting event is subsequently normalized (and have no further subsequent occurance), then the log record indicates this qualification with the '-NORMALIZED' suffix as below: 'normal-NORMALIZED', 'warning-NORMALIZED', 'minor-NORMALIZED', 'major-NORMALIZED', 'critical-NORMALIZED'. 'other' indicates a class of log record, rather than a severity level. The severity level of 'other' is considered less important than 'normal'. 'other' primarily is used to indicate a 'Debug' type of log record. Some log events have configurable severity levels. Others have predetermined (non-configurable) severity levels. At the time this log record was added, or as it replaced another record, the 'logSeverityFilter' allowed this event to be logged. The retrieval of any variable of the 'logRecTable' is effected by the viewing variables, which provide sorting, filtering and page controls. These variables are: 'logViewPageSize', 'logViewPageControl', 'logViewSeverityFilter', 'logViewMethod', 'logViewDirection', 'logViewAge'.