As a network operations engineer, you receive an email message from vRealize Operations Manager with information about one of the data stores for which you are responsible. The email notification informs you about the problem even when you are not presently working in vRealize Operations Manager.
In your email client, you receive an alert similar to the following message.
Alert was updated at Tue Jul 01 16:34:04 MDT : Info:datastore1 Datastore is acting abnormally since Mon Jun 30 10:21:07 MDT and was last updated at Tue Jul 01 16:34:04 MDT Alert Definition Name: Datastore is running out of disk space Alert Definition Description: Datastore is running out of disk space Object Name : datastore1 Object Type : Datastore Alert Impact: risk Alert State : critical Alert Type : Storage Alert Sub-Type : Capacity Object Health State: info Object Risk State: critical Object Efficiency State: info Symptoms: SYMPTOM SET - self Symptom Name | Object Name | Object ID | Metric | Message Info Datastore space usage reaching critical limit datastore1 | b0885859-e0c5-4126-8eba-6a21c895fe1b | Capacity|Used Space | HT above 99.20800922575977 > 95 Recommendations: - Storage VMotion some Virtual Machines to a different Datastore - Delete unused snapshots of Virtual Machines - Add more capacity to the Datastore Notification Rule Name: All alerts -- datastores Notification Rule Description: Alert ID : a9d6cf35-a332-4028-90f0-d1876459032b Operations Manager Server - 192.0.2.0 Alert details
Verify that outbound alerts are configured for standard email alerts. See Add a Standard Email Plug-In for vRealize Operations Manager Outbound Alerts.
Verify that the notifications are configured to send messages to your users for the alert definition. For an example of how to create an alert notification, see User Scenario: Create a vRealize Operations Manager Email Alert Notification.
- In your email client, review the message so that you understand the state of the affected objects and determine if you must begin investigating immediately.
Look for the alert name, the alert state to determine the current level of criticality, and the affected objects.
- In the email message, click Alert Details.
vRealize Operations Manager opens on the Summary tab in the alert details for the generated alert and affected object.
- Review the Summary tab information.
Alert name and description
Review the name and description and verify that you are evaluating the alert for which you received an email message.
Review the top recommendation, and if available, other recommendations, to understand the steps that you must take to resolve the issue. If implemented, will the prioritized recommendations resolve the problem?
What is Causing the Issue?
Which symptoms were triggered? Which were not triggered? What affect does this evaluation have on your investigation? In this example, the alert that the datastore is running out of space is configured so that the criticality is symptom based. If you received a critical alert, then it is likely that the symptoms are already at a critical level, having moved up from Warning and Immediate. Look at the sparkline or metric graph chart for each symptom to determine when the problem escalated on the datastore object.
What to do next
If you determine that the recommendations will resolve the problem, implement them. See Run a Recommendation on a Datastore to Resolve an Alert.
If you need more information about the affected objects, continue your investigation. Begin by looking at other triggered symptoms for the data store. See Evaluate Other Triggered Symptoms for the Affected Data Store.