You define property symptoms, which are based on collected configuration properties, so that you can add one or more symptoms to an alert definition in vRealize Operations Cloud. You use the triggered symptoms to resolve alerts or troubleshoot other problems.
How Property Symptom Definitions Work
A property symptom is triggered when the defined threshold is compared with the current property value and the comparison is evaluated as true.
Where You Find the Property Symptom Definition Workspace
To define symptoms based on metrics or super metrics, in the menu, click Alerts and then in the left pane, click . Click Add to define a property-based symptom in the workspace.
You can also define symptoms as you are defining alerts in the Alert Definition Workspace.
Components that you use to locate the properties for which you are creating symptoms.
|Based Object Type||
Object against which the symptom is evaluated.
Based on the selected object type, the list of available properties displays only the properties applicable to the object type.
If a property is not listed in the common properties list, based on the selected based object type, use Select Resource to inspect the properties of a selected object so that you can locate the property that you must use to create the symptom. Even though you select a property for a specific object, the symptom definition is applicable to all objects with that property in your environment.
Use a word search to limit the number of items that appear in the list.
List of properties for the selected base object type.
|Symptom definition workspace||
Drag the property to the right pane.
The properties are configured values that are compared to the value you specify. You can configure a single property symptom or add multiple symptoms.
For example, if you need an alert when a particular property, such as Memory Hot Add, is no longer at the value required, you can configure a symptom and add it to an alert definition.
Configure the options: