Adaptec iSA1500 User Guide - Page 131

Opening the Event Log, Understanding Severity Levels

Page 131 highlights

Managing Events Opening the Event Log You can view the Event Log at any time by clicking the Events button in the toolbar (shown at right). The Events Search Filter window opens and displays the Event Log. In the Event Log, events are listed with both brief summaries and detailed descriptions of what occurred. To set the event search parameters for viewing the Event Log, see Searching the Event Log on page 7-3. Understanding Severity Levels When events are logged, they are assigned a severity level according to their importance. There are six severity levels: ■ Information-Indicates an event with no impact on the system's functionality. This category is useful for tracing activity by user. ■ Warning-Indicates an event that you should be aware of. Its severity is not sufficient to be considered an error because the system is operating correctly. However, the event may appear unusual to you. For example, the connection to a logical volume fails because one of the disks needed for the volume has been taken off-line- the system is behaving correctly, but this event could pose problems for the user of a database on that volume. In this example, a Warning-level event in the Event Log helps diagnose the problem. 7-2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

7-2
Managing Events
Opening the Event Log
You can view the Event Log at any time by clicking the
Events
button in the toolbar (shown at right).
The Events Search Filter window opens and displays the Event
Log.
In the Event Log, events are listed with both brief summaries and
detailed descriptions of what occurred.
To set the event search parameters for viewing the Event Log, see
Searching the Event Log
on page 7-3
.
Understanding Severity Levels
When events are logged, they are assigned a severity level
according to their importance. There are six severity levels:
Information
—Indicates an event with no impact on the system’s
functionality. This category is useful for tracing activity by user.
Warning
—Indicates an event that you should be aware of. Its
severity is not sufficient to be considered an error because the
system is operating correctly. However, the event may appear
unusual to you.
For example, the connection to a logical volume fails because
one of the disks needed for the volume has been taken off-line—
the system is behaving correctly, but this event could pose
problems for the user of a database on that volume. In this
example, a Warning-level event in the Event Log helps diagnose
the problem.