VMware vROps

Creating an Alert definition and an Alert Notification on VMware vROps

1 Create an alert definition 

In this scenario we will take an existing alert definition then clone it to an alert that we want.

The built-in alert definition that I will be using in this example is “Virtual Machine is demanding more CPU than the configured limit”  .

Log in to  your  vROps – click Home tab, then content icon – then Alert definitions

This displays the built-in alerts that exists in the vROps environment already

As I mentioned earlier we are going to clone an existing alert definition and use it to create a customized alert.

In the list find  “Virtual Machine is demanding more CPU than the configured limit”  . from the top click the clone Icon.

 

And this will take you to a new window.

And let’s work on building our customized alert definition.

Let’s Put the name we want to specify out alert.  Note .. Good naming convention in your vROps environment is very important.

I will suggest to use the following naming convention for your alerting in vROps environment

a)      Acronym of your company – following the alert name/type/or modified

b)      Group or department name - following the alert name/type/or modified ( For larger environment or if you created Capacity based group in your environment

c)       ClusterName – follow by  the alert name/type/or modified ( if you have multiple clusters managed by a simple vROps )

Example:  ITOPSM - Virtual Machine is demanding more CPU than the configured limit

                                                                      Or

                    ITOPSM –VM is demanding more CPU than the configured limit

Anyways something like that..

 Here  we keep the default  unless you need additional information..  you can also remove  the symptom if you don’t want it.

Next we go to Base Object Type.  Because it is a cloned alert definition NOT the newly created alert definition,  The Base Object Type cannot  be modified.  

Next to Alert Impact tab,  You can do the change  as i did on this example  or proceed with what works well for your corporation

 

Next  to Add Symptom Definitions Tab ..  Also in here you can keep the default or modify as you want.

IN CASE you want to add additional Symptom , you can select want is in the symptom list or create a new one by clicking the green +  Then find CPU / demand% or as you would like .. Then DRAG it to right side of the Add  Symptom Definition  windows. Click save when completed.

Next to  Add Recommendations  tab

The add recommendation is there to help you clarify what you need to put in your alert in order to guide system administrator to solve the issue efficiently and easily.

vROps already has default recommendations available for  each type of faulty or malfunction within VMware environment .

In our example we are going to keep the default settings

Click SAVE and the alert definition windows will disappears.

We just created an alert definition.  You modify it as you want.

2- Create an Alert Notification:

In the same Window click Notification 

 

Click the plus green sign to create a new alert notification 

-          Define the name of your Notification

-           your email address or email list

-          All the changes or words you might want to see in your alert

-           

In Filtering Criteria,  you should define the object that you want to monitor

Specify The alert definition that we created in this Example

Click Save when Completed  and you  you will be ready to receive alerts about Virtual machines that demands more CPU