You define metric event symptoms, which are based on reported violations of metric thresholds from monitored systems, so that you can create one or more of the symptoms that you can add to an alert definition in vRealize Operations Manager.

How Metric Event Symptom Definitions Work

A metric event symptom is triggered when vRealize Operations Manager receives a metric event for the metric and event type defined in the symptom. The event type specifies whether the metric is above, below, equal to, or not equal to the threshold set on the monitored system.

Where You Find the Metric Event Symptom Definition Workspace

To define symptoms based on metric events, in the left pane, in the menu, click Alerts and then in the left pane, click Alert Settings > Symptom Definitions. Select the Metric Event tab and 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.

Table 1. Symptoms Workspace Options for Metric Events

Option

Description

Metric Explorer

Components that you use to create symptoms.

Based Object Type

Object against which the symptom is evaluated.

Based on the select object type, the list of available metrics displays only the metrics applicable to the object type.

Select Resource

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.

Search

Use a word search to limit the number of items that appear in the list.

Metric Event list

List of the metric events for the selected base object type.

Symptom definition workspace

Click and drag the metric to the right pane.

Metric Event

You can configure a single threshold or add multiple thresholds.

For example, configure a symptom where, when the virtual machine CPU usage is above the threshold defined in the monitored system, the metric event is above the threshold on the system.

Configure the options:

  • Event type. Select whether the metric is above, below, equal to, or not equal to the threshold set on the monitored system.

  • Criticality level. Severity of the symptom when it is triggered.

  • Symptom name. Name of the symptom as it appears in the symptom list when configuring an alert definition, as it appears when the alert is generated, and when viewing triggered symptoms.

  • Wait Cycle. The trigger condition should remain true for this number of collection cycles before the symptom is triggered. The default value is 1, which means that the symptom is triggered in the same collection cycle when the condition became true.

  • Cancel Cycle. The symptom is canceled after the trigger condition is false for this number of collection cycles after which the symptom is cancelled. The default value is 1, which means that the symptom is canceled in the same cycle when the condition becomes false.