You define fault symptoms, which are based on events published by the monitored systems, so that you can add one or more symptoms to an alert definition. You use the triggered symptoms to resolve alerts or troubleshoot other problems in vRealize Operations Cloud.
How Fault Symptom Definitions Work
A fault symptom is triggered when a fault is active on the base object because of the occurrence of any of the fault events selected in the symptom definition.
Where You Find the Fault Symptom Definition Workspace
To define symptoms based on fault message events, from the left menu, click Symptom Definitions. Select the Fault tab and click Add to define a property-based symptom in the workspace., and then in the right pane, click
You can also define symptoms as you are defining alerts in the Alert Definition Workspace.
Components that you use to create symptoms.
|Based Object Type||
Object against which the symptom is evaluated.
Select the fault definition for the selected base object type.
Some object types do not have fault definitions, and other types have multiple definitions.
|Symptom definition workspace||
Drag the fault definition to the right pane.
|Fault symptom definition||
The fault events are published events from monitored systems. You can configure a single fault event symptom or add multiple symptoms.
For example, if your base object is host and you drag the Hardware sensor fault for unknown type fault definition, you then select one of two text strings indicating a fault.
Configure the options: