Which three types of data are considered as potential evidence in the Troubleshooting Workbench?

 The Troubleshooting Workbench is a feature in vRealize Operations that helps you perform advanced troubleshooting tasks on an alert or an object. You can look for potential evidences of a problem within a specific scope and time range. The potential evidences are based on three types of data: Alerts, Events, and Property Changes. Alerts show the active and inactive alerts that are related to the object or its peers. Events show the events that are based on a change in the metrics, such as spikes, drops, or anomalies. Property Changes show the changes in the configuration or properties of the object or its peers, such as CPU, memory, or disk allocation. These types of data help you identify the root cause of the issue and take corrective actions. Symptoms and Anomalous Metrics are not considered as potential evidence in the Troubleshooting Workbench, although they may be used to trigger alerts or events. Logs are not displayed in the Troubleshooting Workbench, but they can be accessed from the Logs tab of the object. References: Discovering Potential Evidences Using the Troubleshooting Workbench, Solving Real Problems with vRealize Operations TroubleshootingWorkbench, Troubleshooting Workbench Home Page, vROps 8.0 Troubleshooting Workbench and Blue Medora