The Faults badge quantifies the severity of problems the selected object is experiencing.
The Faults score is calculated based on events published by the vCenter Server. This score includes events like loss of redundancy in NICs or HBAs, memory checksum errors, HA failover problems, CIM events, and so on. Faults are included in the health score because they require immediate resolution, while items that contribute to the risk score might not be immediate, but still require your attention.
Each resource in vRealize Operations Manager has a faults score ranging from 0 (no faults) to 100 (critical faults). The scores are computed based on the severity of the underlying problems. When more than one fault-related problems exists on the resource, the faults score is based on the most severe problem.
The higher the Faults score, the lower the resulting health for that resource. Resolution of the problem indicated by the Fault will restore the resource's health score.
While the Faults score ranges between 0 to 100, the badge changes color based on the badge score thresholds that are set by the vRealize Operations Manager administrator. For example, a green Faults badge can indicate a score below 40 instead of a score below 25 (the system default).
Unlike other badges in vRealize Operations Manager, the Faults badge does not have an alert generated from its threshold score. Instead, each problem generates its own fault alert, and resolution of the problem both clears or cancels the alert and lowers the badge score.
|Badge Icon||Description||User Action|
|No faults are registered on the selected object.||No attention required.|
|Faults of low importance are registered on the selected object.|
|Faults of high importance are registered on the selected object.|
|Faults of critical importance are registered on the selected object.|
|No data is available or the object is offline.|