# Conjoined Performance and Trace data
For complex debugging, it can at times be easier to conjoin performance views with trace data. To do this, download the performance data after a trace has been started. You will receive the option to include the trace:
Retrieve trace
The result of doing this is a new list box showing up in the performance view, immediately after the rule name:
Qwerty rule set
The list box offers either the regular performance data or a view by transaction:
list box
For assistance, the URI variable used by almost all input adaptors is displayed to help determine a relevant transaction. Once a transaction is selected, the performance display will change:
Selected transaction
You are now only seeing the entry count for each rule *(for data volume reasons, exit points are not shown)*.
At any point you can now see the state of the variables at each entry point, simply by clicking on it:
state of variables
If you have loops in your rule sets, more than one transaction can be seen at the entry point of a rule:
Loop in the rule set
Clicking on that entry point allows you to iterate through each invocation, one by one:
