Wednesday, March 24, 2010

5 things you need to know about VMware vSphere Alarms

By David Davis from

Virtualization is an awesome thing but just like any piece of your IT infrastructure, you need to be alerted when something goes wrong
(and ideally, before something goes wrong). VMware vSphere has a powerful alerting or notification system built in called "Alarms" (call them whatever you want but if you want to use them in vSphere, you should start calling them "alarms"). Alarms can be configured to tell you when specific events, conditions, or states occur within the vSphere inventory.

Let's learn the 5 most important things you need to know about vSphere alarms.
  1. vSphere has 33 pre-configured and enabled alarms
  2. Alarms trickle down the vSphere inventory hierarchy
  3. vSphere has a Triggered Alarms and an Alarm Definitions View
  4. vSphere has 8 Alarm monitoring types
  5. An Alarm is defined by with a type, trigger, and action
In point #5, we learn that creating a new alarm is easy by following my simple 7 steps. Overall, it is crucial for vSphere Admins to understand how alarms work in order to properly monitor their virtual infrastructure and to be alerted of issues that need to be resolved. I encourage you to spend a few minutes working with vSphere alarms!
Step by Step Guide to learn above 5 Things --> Link here from

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.