Message event symptoms are based on message events received from a component of vRealize Operations Cloud or from an external monitored system through the system's REST API. You define message event systems so that you can create one or more of the symptoms that you can add to an alert definition.
How Message Event Symptom Definitions Work
A message event symptom is triggered when a message in an incoming event matches the text string in the symptom based on the specified operator.
Where You Find the Message Event Symptom Definition Workspace
To define symptoms based on message events, in the menu, click Alerts and then in the left pane, click . Select the Message 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.
Near Real-Time Monitoring is triggered automatically if the adapter instance has real-time monitoring enabled.
|Message Event Selector||
Components that you use to create symptoms.
|Based Object Type||
Object against which the symptom is evaluated.
|Select the Type of Event||
Select the type of incoming event against which you are matching the events as they arrive. The incoming event must contain the following type and subtype combinations.
|Symptom definition workspace||
Drag the event type to the right pane.
The Message Event text string is compared to the message in the incoming event by using the specified operator. You can configure a single message event symptom or add multiple symptoms.
For example, the VMware adapter sends a change event when the CPU limit for a virtual machine was changed from unlimited to 2 GHz. You can create a symptom to detect CPU contention issues as a result of this configuration change.
Configure the options: