jump to navigation

VMware alarms, there;s two types, read on July 13, 2012

Posted by vbry21 in VMware blogs.

I was asked a question about alarms in VMware, the question was.

“What is the difference between, event based alarms and condition based alarms?”

Here goes.

You configure alarm triggers to generate warnings and alerts when the specified triggers are 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. Conditions or states include power states, connection states, and performance metrics such as CPU and disk usage.

Event triggers – Monitor events that occur in response to operations occurring with a managed object in the inventory or the vCenter Server system itself. For example, an event is recorded each time a virtual machine (which is a managed object) is cloned, created, deleted, deployed, and migrated.

On our Vsphere 5 ICM or Fastrack, there’s a lab that allows the delegates to create alarms.

The first alarm is a condition based alarm, we monitor for CPU usage within the VM, when the CPU utilisation exceeds the trigger value the alarm triggers and the VM suspends.

We then create a second alarm, this time an event based alarm, and the event we monitor for is a suspended VM, with this alarm we get an Alert to tell us the alarm has triggered.

To see a demo click this link



No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: