Synthetic Classic has reached end of support and is no longer available. Existing Synthetic Classic customers have been upgraded to the all-in-one Dynatrace software intelligence platform.

Problem analysis

If the test has errors or performance problems:

  • The anomalies chart in the Test overview page identifies test executions with anomalies. Select a datapoint to view summary information about an anomaly. Click the anomalies tile to drill down to the Problem analysis page.

  • The Waterfall summary page includes an Analysis section that identifies the page (step) where the issues occurred, and provides summary information for the issues that contributed to the overall problem. Click Analyze problems to go to the Problem analysis page for more details.

Problem analysis page

The Problem analysis page shows information for the 6-hour period ending with the selected test execution, so you can analyze the problem in context and zero in on the root causes.

The page shows the problem type, the affected location, the start and end time of the 6-hour analysis period, and the top contributing issues for the problem.

To examine one problem type and/or one affected test step, make selections from the Analyze lists at the top of the page. You can also click the Top contributors above the chart to hide/show the selected item in the Top contributors list.

Expand Expand icon an item in the Top contributors list at the bottom of the page to see the details, including information about the leading contributor to the problem and response times charted against a dynamic threshold. Hover over a datapoint in the chart to see the timestamp, response times for the step and the top contributing object, and the error code if an error occurred.

Charting the step performance and the top contributor's performance together can help you zero in on the underlying cause of the problem. For example, show you that the same object may be a factor in each response time spike. Or, you may see that performance was normal up to the test execution where the problem occurred, so you should look for a recent event that affected the test. Identifying the top contributing object can also tell you whether a third-party contributor is affecting your web page.