You can enable or disable alert and symptom definitions to have vRealize Operations Manager identify problems on objects in your environment and trigger alerts when conditions occur that qualify as problems. You can automate alerts.
How the Alert and Symptom Definitions Workspace Works
vRealize Operations Manager collects data for objects and compares the collected data to the alert definitions and symptom definitions defined for that object type. Alert definitions include associated symptom definitions, which identify conditions on attributes, properties, metrics, and events.
You can configure your local policy to inherit alert definitions from the base policies that you select, or you can override the alert definitions and symptom definitions for your local policy.
Before you add or override the alert definitions and symptom definitions for a policy, familiarize yourself on the available alerts and symptoms.
To view the available alert definitions, select Content and click Alert Definitions.
To view the available symptom definitions, select Content and click Symptom Definitions. Symptom definitions are available for metrics, properties, messages, faults, smart early warnings, and external events.
A summary of the number of problem and symptoms that are enabled and disabled, and the difference in changes of the problem and symptoms as compared to the base policy, appear in the Analysis Settings pane of the policies workspace.
Where You Override the Alert Definitions and Symptom Definitions
To override the alert definitions and symptom definitions for your policy, click Administration, click Policies, click the Policy Library tab, and click the plus sign to add a policy or click the pencil to edit a policy. In the Add or Edit Monitoring policy workspace, on the left click Alert / Symptom Definitions. The definitions appear in the workspace.
Policy Alert Definitions and Symptom Definitions
You can override the alert definitions and symptom definitions for each policy.