VMware 4817V62 Administration Guide - Page 234

Alarm Triggers, Condition and State Triggers - api

Page 234 highlights

vSphere Basic System Administration Action You can set alarms to trigger when the state changes from green to yellow, yellow to red, red to yellow, and yellow to green. Triggers are defined for the default VMware alarms. You can change the trigger conditions (thresholds, warning values, and alert values) for the default alarms. The operation that occurs in response to the trigger. For example, you can have an email notification sent to one or more administrators when an alarm is triggered. The default vCenter Server alarms are not preconfigured with actions. You must manually set what action occurs when the triggering event, condition, or state occurs. NOTE Some alarms contain triggers that are not supported in the vSphere Client and cannot be changed. However, you can still configure the alarm actions, enable or disable the alarm, and change the alarm name. If your environment requires changes to these alarm triggers, create custom alarms by using the vSphere Client or the VMware vSphere APIs. This chapter includes the following topics: n "Alarm Triggers," on page 234 n "Alarm Actions," on page 243 n "Alarm Reporting," on page 248 n "Creating Alarms," on page 248 n "Managing Alarms," on page 252 n "Managing Alarm Actions," on page 256 n "Preconfigured VMware Alarms," on page 259 Alarm Triggers You configure alarm triggers to generate warnings and alerts when the specified criteria is met. Alarms have two types of triggers: condition or state triggers, and event triggers. Condition or State Triggers Monitor the current condition or state of virtual machines, hosts, and datastores. This includes power states, connection states, and performance metrics, such as CPU and disk usage. To set alarms on other objects in the inventory, including datacenters, clusters, resource pools, and networking objects, use event triggers. NOTE You can set a condition or state alarm at the datacenter level that monitors all virtual machines, hosts, or datastores in the datacenter. Event Triggers Monitors events that occur in response to operations occuring with any managed object in the inventory, the vCenter Server system, or the license server. For example, an event is recorded each time a virtual machine is cloned, created, deleted, deployed, and migrated. Condition and State Triggers Use condition triggers and state triggers to set alarms on performance metrics, power states, and connection states for virtual machines, hosts, and datastores. To set alarms on other objects in the inventory, you must use event triggers. Condition and state triggers use one of the following operator sets to monitor an object: n Is equal to and Is not equal to 234 VMware, Inc.

  • 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

You can set alarms to trigger when the state changes from green to yellow,
yellow to red, red to yellow, and yellow to green. Triggers are defined for the
default VMware alarms. You can change the trigger conditions (thresholds,
warning values, and alert values) for the default alarms.
Action
The operation that occurs in response to the trigger. For example, you can have
an email notification sent to one or more administrators when an alarm is
triggered. The default vCenter Server alarms are not preconfigured with
actions. You must manually set what action occurs when the triggering event,
condition, or state occurs.
N
OTE
Some alarms contain triggers that are not supported in the vSphere Client and cannot be changed.
However, you can still configure the alarm actions, enable or disable the alarm, and change the alarm name.
If your environment requires changes to these alarm triggers, create custom alarms by using the vSphere Client
or the VMware vSphere APIs.
This chapter includes the following topics:
n
“Alarm Triggers,”
on page 234
n
“Alarm Actions,”
on page 243
n
“Alarm Reporting,”
on page 248
n
“Creating Alarms,”
on page 248
n
“Managing Alarms,”
on page 252
n
“Managing Alarm Actions,”
on page 256
n
“Preconfigured VMware Alarms,”
on page 259
Alarm Triggers
You configure alarm triggers to generate warnings and alerts when the specified criteria is met. Alarms have
two types of triggers: condition or state triggers, and event triggers.
Condition or State
Triggers
Monitor the current condition or state of virtual machines, hosts, and
datastores. This includes power states, connection states, and performance
metrics, such as CPU and disk usage. To set alarms on other objects in the
inventory, including datacenters, clusters, resource pools, and networking
objects, use event triggers.
N
OTE
You can set a condition or state alarm at the datacenter level that
monitors all virtual machines, hosts, or datastores in the datacenter.
Event Triggers
Monitors events that occur in response to operations occuring with any
managed object in the inventory, the vCenter Server system, or the license
server. For example, an event is recorded each time a virtual machine is cloned,
created, deleted, deployed, and migrated.
Condition and State Triggers
Use condition triggers and state triggers to set alarms on performance metrics, power states, and connection
states for virtual machines, hosts, and datastores. To set alarms on other objects in the inventory, you must use
event triggers.
Condition and state triggers use one of the following operator sets to monitor an object:
n
Is equal to
and
Is not equal to
vSphere Basic System Administration
234
VMware, Inc.