VMware 4817V62 Administration Guide - Page 239

Event Trigger Components, Virtual Machine Event Triggers, Table 21-7.

Page 239 highlights

Chapter 21 Working with Alarms Table 21-7. Example - Event Arguments, Operators, and Values Argument Operator Value group equal to Fan newState equal to Yellow NOTE Due to the large number of events tracked by vCenter Server, the event table for each object does not contain definitive lists of events. Instead, it provides a subset of the events available for alarm triggers. Event Trigger Components Event triggers are composed of a trigger type, a trigger status, and triggering conditions. Table 21-8 describes the components of event alarm triggers. Table 21-8. Event Trigger Components Trigger Component Description Trigger type Status Conditions Event to monitor. Events can be generated by a user action or the system, for example, Account Password Change and Alarm Email Sent. The value that must be met for the alarm to trigger: n Normal n Warning n Alert. Specifications that define the trigger. Event conditions include the following components: n Argument - The event attribute to monitor. n Operator - The qualifier used to set the trigger value, for example Starts with and Doesn't start with. n Value - The value that must be met to trigger the event. Conditions are not configurable for all events. For example, you have a subset of hosts in the same datacenter named with the identifying prefix, QA_. To trigger an alarm when any of these hosts lose network connectivity, create an alarm on the datacenter to monitor the event Lost Network Connectivity. The trigger conditions are: n Argument - host.name n Operator - Starts with n Value - QA_ When storage connectivity is lost on a host named QA_Host1, the event triggers. Event triggers do not rely on thresholds or durations. They use the arguments, operators, and values to identify the triggering condition. When the triggering conditions are no longer true, a triggered alarm resets automatically, and no longer triggers. Virtual Machine Event Triggers VMware provides preconfigured alarms that trigger when events occur on virtual machines. Table 21-9 lists events you can use to trigger alarms on virtual machines. VMware, Inc. 239

  • 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
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364

Table 21-7.
Example – Event Arguments, Operators, and Values
Argument
Operator
Value
group
equal to
Fan
newState
equal to
Yellow
N
OTE
Due to the large number of events tracked by vCenter Server, the event table for each object does not
contain definitive lists of events. Instead, it provides a subset of the events available for alarm triggers.
Event Trigger Components
Event triggers are composed of a trigger type, a trigger status, and triggering conditions.
Table 21-8
describes the components of event alarm triggers.
Table 21-8.
Event Trigger Components
Trigger Component
Description
Trigger type
Event to monitor. Events can be generated by a user action or the system, for example,
Account Password Change and Alarm Email Sent.
Status
The value that must be met for the alarm to trigger:
n
Normal
n
Warning
n
Alert.
Conditions
Specifications that define the trigger.
Event conditions include the following components:
n
Argument – The event attribute to monitor.
n
Operator – The qualifier used to set the trigger value, for example
Starts with
and
Doesn’t start with
.
n
Value – The value that must be met to trigger the event.
Conditions are not configurable for all events.
For example, you have a subset of hosts in the same datacenter named with the identifying prefix,
QA_.
To
trigger an alarm when any of these hosts lose network connectivity, create an alarm on the datacenter to monitor
the event
Lost Network Connectivity
. The trigger conditions are:
n
Argument —
host.name
n
Operator —
Starts with
n
Value –
QA_
When storage connectivity is lost on a host named QA_Host1, the event triggers.
Event triggers do not rely on thresholds or durations. They use the arguments, operators, and values to identify
the triggering condition. When the triggering conditions are no longer true, a triggered alarm resets
automatically, and no longer triggers.
Virtual Machine Event Triggers
VMware provides preconfigured alarms that trigger when events occur on virtual machines.
Table 21-9
lists events you can use to trigger alarms on virtual machines.
Chapter 21 Working with Alarms
VMware, Inc.
239