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.
How the Policy Symptom Definitions Work
vRealize Operations 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 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.
Where You Modify the Policy Symptom Definitions
To modify the policy package of symptoms, from the left menu click , and then click Add to add a policy or select the required policy. In the right pane, click Edit Policy to edit a policy. In the Create or Edit policies workspace, click Alerts and Symptoms. The alert definitions and symptom definitions for the selected object types appear in the workspace.
| Option | Description |
|---|---|
| Actions | Select one or more symptom definitions and select enable, disable, or inherit to change the state for this policy. |
| Filter options |
Deselect the options in the
Type and
State drop-down menus, to narrow the list of symptom definitions.
Type 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. State determines whether enabled, disabled, and inherited symptom definitions appear in the symptom definition list. |
| Object Type | Filters the symptom definitions list by object type |
| Page Size | The number of symptom definitions to list per page. |
| Filter | 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.
|
Enabled. Indicates that a symptom definition will be included. 
Disabled. Indicates that a symptom definition not be included. 
Inherited. Indicates that the state of this symptom definition is inherited from the base policy and will be included. 
Inherited. Indicates that the state of this symptom definition is inherited from the base policy and will not be included. If you do not configure the package, the policy inherits the settings from the selected base policy.
