Each policy includes a package of symptom definitions. Each symptom represents a distinct test condition on a property, metric, or event. You can enable or disable the symptom definitions in your policy.

vRealize Operations Manager uses symptoms that are enabled to generate alerts. When the symptoms used in an alert definition are true, and the alert is enabled, an alert is generated.

When a symptom exists for an object, the problem exists and requires that you take action to solve it. When an alert occurs, vRealize Operations Manager presents the triggering symptoms, so that you can evaluate the object in your environment, and with recommendations for how to resolve the alert.

To assess objects for symptoms, you can include symptoms packages in your policy for metrics and super metrics, properties, message events, and faults. You can enable or disable the symptoms to determine the criteria that the policy uses to assess and evaluate the data collected from the objects to which the policy applies. You can also override the threshold, criticality, wait cycles, and cancel cycles.

The Symptoms pane displays the name of the symptom, the associated management pack adapter, object type, metric or property type, a definition of the trigger such as for CPU usage, the state of the symptom, and the trigger condition. To view a specific set of symptoms in the package, you can select the adapter type, object type, metric or property type, and the state of the symptom.

When a symptom is required by an alert, the state of the symptom is enabled, but is dimmed so that you cannot modify it. The state of a required symptom includes an information icon that you can hover over to identify the alert that required this symptom.

To modify the policy package of symptoms, 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 Override Alert / Symptom Definitions. The alert definitions and symptom definitions for the selected object types appear in the workspace.

Symptom Definitions in the Add or Edit Monitoring Policy Workspace




Select all symptom definitions so that you can update their state simultaneously to enable, disable, or inherit them, or deselect all definitions.


Determines whether symptom definitions that apply to HT and DT metrics, properties, events such as message, fault, and metric, and smart early warnings appear in the list.


Determines whether enabled, disabled, and inherited symptom definitions appear in the symptom definition list.

Object Type

Filters the view to an object type to view the symptom definitions.

Per Page

The number of symptom definitions to list per page.


Locate data in the symptom definition list.

Symptom Definitions data grid

Displays information about the symptom definitions for the object types. The full name for Symptom Definition appears in a tooltip when you hover the mouse over the Symptom Definition name.

Name. Symptom definition name as defined in the list of symptom definitions in the Content area.

Adapter. Data source type for which the alert is defined.

Object Type. Type of object to which the alert applies.

Type. Object type on which the symptom definition must be evaluated.

Trigger. Static or dynamic threshold, based on the number of symptom definitions, the object type and metrics selected, the numeric value assigned to the symptom definition, the criticality of the symptom, and the number of wait and cancel cycles applied to the symptom definition.

State. Symptom definition state, either enabled, disabled, or inherited from the base policy.

Condition. Enables action on the threshold. When set to Override, you can change the threshold. Otherwise set to default.

Threshold. To change the threshold, you must set the State to Enabled, set the condition to Override, and set the new threshold in the Override Symptom Definition dialog box.

If you do not configure this package, the policy inherits the settings from the selected base policy.