By clicking on a business transaction you display the E2E Trace. By default the most expensive step of the trace is first displayed.
You can either use the carousel ( < and > ) to choose another step or click in the breadcrumb on Transaction Steps.
The screen shows in the upper part the Client-Server analysis and below the Server Analysis.
Client Server Analysis
Explanation of Times
This time contains the client preprocessing time (cPT) and the client response times (cRespT) of cached requests. Client rendering time (cRendT) is not included in the Client time because this time is not atomic and would lead for nested pages to completely wrong values.
This time is the time difference between the timestamp when client really begins to send data and the timestamp when the client is ready to send data. The time for HTTP request to wait for certain condition to begin data transfer is counted as blocked time.
Network time between browser and server
The network time per HTTP request between the browser and the first HTTP server component is calculated as the difference of the client response time and the server time (see picture below).
Server gross time
This is the time spent in the HTTP servers connected by the browser. Requests from this HTTP server (via RFC or HTTP) to other components are included in the server time but not accumulated additionally.
Client Rendering time
This is the time required for rendering the page and loading sub-requests.
This time is the approx server gross time when the server logs are not uploaded or collected. The precondition to calculate it is that the network layer events are available.
HTTP Analysis Summary
The pie chart displays gives you an overview how the overall response time of this step is distributed. Is it more server, network or client related. The bar chart displays the top expensive requests.