Trace View helps to trace HTTP messages sent from an application to a proxy and it helps analyze data right from the starting of the request till a response received by the application.

Click the Trace View  icon present on the sidebar to switch to the Live Session screen. Click the Server Group name where tracing need to be performed.

Figure 1: Trace View option inside a project

Clicking the Start Trace Session  button present on the upper-left part of the screen starts tracing the request.


As the tracing starts, Stop Trace Session button gets enabled, clicking on which tracing will be stopped.

Figure 2: Trace View page with the Start Trace Session option in enabled state

Whenever requests are sent, the details such as URI, Method, Status, and Timestamp appear under the Transactions table. These values get populated following the time interval as configured in the Automatic Refresh Interval or upon clicking the Refresh button.

Provide the Timeout value depending on the time required till the tracing needs to be done. Elapsed Time can be seen next to the Timeout property.

Figure 3: Trace View section in tracing stage

Details of each session

By clicking the policy icon, details of the request before executing (Incoming) the policy as well as after execution (Outgoing) will be displayed below the policies. Details such as Context Variable, Payload, Form Parameters and Headers will be displayed by clicking the respective tab.

Figure 5: Details of XML2JSON policy displayed

Download Trace Session button helps download the data in JSON format to the designated Download directory.

Filtering the Transactions data

Expand the Filters tab to configure the data that needs to be filtered.

Provide the details (URI, Proxy Method, Proxy Status, Target Method, Target Status, From Date and To Date) under the Filters section based on which the transactions need to be traced and then click the Save icon.

Figure 4: Options to filter transactions

Adaptavist ThemeBuilder EngineAtlassian Confluence