# 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:

<figure><img src="/files/jnhI6Awm768BVYdooJ4M" alt=""><figcaption><p>Retrieve trace</p></figcaption></figure>

The result of doing this is a new list box showing up in the performance view, immediately after the rule name:

<figure><img src="/files/6Tw50HdUcSGSf4GFlYnR" alt=""><figcaption><p>Qwerty rule set</p></figcaption></figure>

The list box offers either the regular performance data or a view by transaction:

<figure><img src="/files/QXF2Zitkzb8kv3dNWTEc" alt=""><figcaption><p>list box</p></figcaption></figure>

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:

<figure><img src="/files/EoVPhy4zsNmgi6vrwaYx" alt=""><figcaption><p>Selected transaction</p></figcaption></figure>

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:

<figure><img src="/files/MrbzKEFQlulhIJFwIwAt" alt=""><figcaption><p>state of variables</p></figcaption></figure>

If you have loops in your rule sets, more than one transaction can be seen at the entry point of a rule:

<figure><img src="/files/ACfUa1BrujVmWJHvLWKJ" alt=""><figcaption><p>Loop in the rule set</p></figcaption></figure>

Clicking on that entry point allows you to iterate through each invocation, one by one:

<figure><img src="/files/xEzeYf4EWGvHmJdESLgY" alt=""><figcaption><p>Iterate through each invocation</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tomorrowx.com/cap/product-reference/conjoined-performance-and-trace-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
