Which three types of data are considered as potential evidence in the Troubleshooting Workbench? (Choose three.)

Question

Options

• ASymptoms
• BAlerts
• CEvents
• DProperty Changes
• EAnomalous Metrics
• FLogs

• B
  4% (2)
• C
  94% (44)
• F
  2% (1)

Explanation

In the Troubleshooting Workbench (as found in platforms like Dynatrace), Events (C), Property Changes (D), and Anomalous Metrics (E) are the three designated evidence types because they represent objective, system-generated signals that can be correlated to pinpoint root causes - they are what happened, what changed, and what deviated from normal. Symptoms (A) are the user-observed or high-level problem descriptions that prompt an investigation, not raw evidence fed into the workbench. Alerts (B) are notifications triggered by thresholds being crossed, making them a downstream reaction rather than a core evidence type. Logs (F), while valuable for debugging generally, are not one of the three classified evidence types within the Troubleshooting Workbench's specific data model.

Memory tip: Use the acronym EPA - Events, Property changes, Anomalous metrics. Think of the workbench as an investigator gathering EPA evidence at a crime scene: something happened (event), something was altered (property change), and something went off the charts (anomalous metric).

No community discussion yet for this question.