Performance: APM+ Requests

While in the Performance (APM+) tab within the App Dashboard there is a sub tab called By Requests. The By Requests tab allows you detailed insight into your applications request chain as well as information on the traces that are taken.

By clicking on the requested actions link listed below the Satisfaction chart, you will be taken to an individual detailed view of a specific request. Here you can see a similar Satisfaction chart that is  time specific to the requested action that you selected.  You can also see a Request Performance Breakdown that will list different categories that make up the request, which also includes SQL queries performed in the request.

If any exceptions occurred for this requested action and you have Errors and Logs configured, you will see exceptions listed here as well.


Performance Breakdown also displays the available traces in each request. Clicking on any available trace icon will give you more information on that particular trace. The colors correspond to how long the trace took- grey is under 200ms, orange is between 200 and 500ms, red is between 500 and 1 second, and a darker red is for all traces over 1 second.
There is also filter tabs for Traces that selects the Slowest, Fastest, and Latest Trace. All Traces lists every Trace that Retrace has captured. You can click on the occurrence of each individual trace to see the method call breakdown of that trace.

Once you select a Trace a chart is displayed highlighting different App components and comparing that particular trace with the average time period of the past 24 hours. Below that chart is a method call tree that organizes all the methods of the trace into a tree-like breakdown. Along with a breakdown of the stack trace is the % of time and total time each method took.

If you have Errors and Logs configured, any logging statements that are called within the trace will appear here inline in the method. If there are any exceptions listed in your trace, you can click on the red bug icon to view error details or you can expand any debug data to view the JSON document.

You can expand any SQL query sections that appear in the trace to see the query, or you can click on the link of SQL statement to see that query’s performance.