# Viewing the Complete Performance Report

The complete performance report is available when the performance collection level is set to "All counters". The full report includes all of the statistics described in the previous sections, plus a URI level report and database pool statistics

The database pool report provides a view of the size of the database pool and the number of live connections *(connections handed out to the* <code class="expression">space.vars.X\_Agent\_Name\_Single</code>*)*, spaced out over the life of the <code class="expression">space.vars.X\_Agent\_Name\_Single</code>. The timeline will compress depending on the time the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> has been running.

<figure><img src="/files/PUn0ypzvfKzgODleJudH" alt=""><figcaption><p>Visualization for Cases</p></figcaption></figure>

<figure><img src="/files/0uHfv2zJZtO9zr6O5Sy5" alt=""><figcaption><p>Visualization for History pool</p></figcaption></figure>

The URI level report is divided into 2 sections. The first section provides a summary of the highest <code class="expression">space.vars.X\_Agent\_Name\_Single</code> delays measured for each URI in descending order from the highest to the lowest. This measurement does NOT include the very first transaction for each URI. It is a useful measure to quickly identify rule set hot-spots in very large rule sets.

<figure><img src="/files/IjceiHbeQx8LfUsvFNXB" alt=""><figcaption><p>Transaction Level Performance Statistics</p></figcaption></figure>

The second section provides a quick view of individual URI response times (or all URIs combined if `"*"` is selected). There are up to three of these distribution diagrams:

1. Performance with <code class="expression">space.vars.X\_Agent\_Name\_Single</code> stopped. This diagram is only present if data has been collected with the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> stopped. This can be achieved by stopping a configuration and continuing to undertake transactions.
2. Performance with <code class="expression">space.vars.X\_Agent\_Name\_Single</code> started. This diagram provides information about the combined delay of the application and the <code class="expression">space.vars.X\_Agent\_Name\_Single</code>.
3. Performance of <code class="expression">space.vars.X\_Agent\_Name\_Single</code> alone. This diagram provides information about the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> alone. Application response times are automatically deducted from the result. However, any calls to external services or databases are still included.


---

# 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/performance-data/viewing-the-complete-performance-report.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.