6.3

Table Of Contents
The following actions are supported for automation:
n
Delete Powered O VM
n
Delete Idle VM
n
Move VM
n
Power O VM
n
Power On VM
n
Set CPU Count And Memory for VM
n
Set CPU Count And Memory for VM Power O Allowed
n
Set CPU Count for VM
n
Set CPU Count for VM Power O Allowed
n
Set CPU Resources for VM
n
Set Memory for VM
n
Set Memory for VM Power O Allowed
n
Set Memory Resources for VM
n
Shut Down Guest OS for VM
How to Use Alerts and Actions Together for Automation
(hp://link.brightcove.com/services/player/bcpid2296383276001?
bctid=ref:video_vrealize_alerts_actions_automation)
How to Automate an Alert that has an Associated Action
(hp://link.brightcove.com/services/player/bcpid2296383276001?
bctid=ref:video_vrom_automate_alert_with_action)
How to Create and Automate a New Alert with a Symptom Denition and Action
(hp://link.brightcove.com/services/player/bcpid2296383276001?
bctid=ref:video_vrom_create_alert_automate_symptom_denition)
Roles Needed to Automate Actions
To automate actions, your role must have the following permissions:
n
Create, edit, and import policies in Administration > Policy Management.
n
Create, clone, edit, and import alert denitions in Content > Alert  Management.
n
Create, edit, and import recommendation denitions in Content > Recommendations Management.
I You set the permissions used to run the actions separately from the alert and recommendation
denition. Anyone who can modify alerts, recommendations, and policies can also automate the action,
even if they do not have permission to run the action.
For example, if you do not have access to the Power O VM action, but you can create and modify alerts and
recommendations, you can see the Power O VM action and assign it to an alert recommendation. Then, if
you automate the action in your policy, vRealize Operations Manager uses the automationAdmin user to run
the action.
vRealize Operations Manager User Guide
60 VMware, Inc.