Add a Virtual Machine
CPU Usage Symptom to the Alert Definition
To generate alerts related to CPU usage
on your accounting virtual machines, you add symptoms to your
VMware Aria
Operations
alert definition after you provide the basic descriptive information
for the alert. The first symptom you add is related to CPU usage on virtual machines. You
later use a policy and group to apply alert to the accounting virtual machines. Begin configuring the alert
definition. See
Add Description and Base Object to Alert Definition.
This scenario has two
symptoms, one for the accounting virtual machines and one to monitor the hosts
on which the virtual machines operate.
- In theAlert Definition Workspacewindow, after you configure theName and Description,Base Object Type, andAlert Impact, clickNextand configure the symptoms.
- Begin configuring the symptom set related to virtual machines CPU usage.
- From theSelect Symptomdrop-down menu, selectMetric / Property.
- From theDefined Ondrop-down menu, selectChild.
- From theFilter by Object Typedrop-down menu, selectVirtual Machine.
- ClickCreate Newto open theAdd Symptom Definitionworkspace window.
- Configure the virtual machine CPU usage symptom in theAdd Symptom Definitionworkspace window.
- From theBase Object Typedrop-down menu, expandvCenter Adapterand selectVirtual Machine.The collected metrics for virtual machines appears in the list.
- In the metrics listSearchtext box, which searches the metric names, typeusage.
- In the list, expandCPUand dragUsage (%)to the workspace on the left.
- From the threshold drop-down menu, selectDynamic Threshold.Dynamic thresholds useVMware Aria Operationsanalytics to identify the trend metric values for objects.
- In theSymptom Definition Nametext box, type a name similar toVM CPU Usage above trend.
- From the criticality drop-down menu, selectWarning.
- From the threshold drop-down menu, selectAbove Threshold.
- Leave theWait CycleandCancel Cycleat the default values of 3.This Wait Cycle setting requires the symptom condition to be true for 3 collection cycles before the symptom is triggered. This wait avoids triggering the symptom when there is a short spike in CPU usage.
- ClickSave.
The dynamic symptom, which identifies when the usage is above the tracked trend, is added to the symptom list. - In theAlert Definition Workspacewindow, dragVM CPU Usage above trendfrom the symptom definition list to the symptom workspace on the left.The Child-Virtual Machine symptom set is added to the symptom workspace.
- In the symptoms set, configure the triggering condition so that when the symptom is true on half of the virtual machines in the group to which this alert definition is applied, the symptom set is true.
- From the value operator drop-down menu, select>.
- In the value text box, enter50.
- From the value type drop-down menu, selectPercent.
You defined the first symptom
set for the alert definition.
Add the host memory usage
symptom to the alert definition. See
Add a Host Memory Usage Symptom to the Alert Definition.