Because you need more information about the data store before you decide on the best response, you examine the Symptoms tab to see other triggered symptoms for the data store.
If other symptoms are triggered for the object besides the symptom included in the alert, evaluate them to determine what the symptoms reflect about the state of the object, and to decide whether the related recommendations might resolve the problem.
Verify that you are addressing the alert for which you received an alert message in your email. See Respond to an Alert in Your Email.
- In the menu, click Alerts and select the alert name in the data grid.
The center pane view changes to display the alert detail tabs.
and review the active symptoms.
Are other symptoms of similar criticality present that are affecting the object?
Are any of the triggered symptoms related to the symptoms that triggered the current alert? Symptoms related to time remaining, capacity, or stress that could indicate storage problems?
Do the date and time stamps for the symptoms indicate that they were triggered before the alert you are investigating, indicating that it might be a related symptom? Were the symptoms triggered after the alert was generated, indicating that the alert symptoms contributed to these other symptoms?
Can you identify a correlation between the alert symptoms and the other symptoms based on the triggering metric values?
What to do next
If your review of the symptoms and the provided information clearly indicates that the recommendations will solve the problem, implement one or more of the recommendations. For an example of implementing one of the recommendations, see Run a Recommendation on a Datastore to Resolve an Alert.
If your review of the symptoms did not convince you that the recommendations will resolve the problem or provide you with enough information to identify the root cause, continue your investigation using the Events > Timeline tab. See Compare Alerts and Events Over Time in Response to a Datastore Alert.