# Insights surfaced elsewhere on Distributional

Distributional’s goal is to provide you the ability to ask and answer the question “Is my AI-powered app behaving as expected?” While testing is a key component of this, triage of a failed test and inspiration for new tests can come from many places in our web UI. Here, we show insights into app behavior which are uncovered with Distributional.

## Run Detail page

Because each Run represents the recent behavior of your app, the Run Detail page is a useful source of insights about your app’s behavior.  In the screenshot below, you can see:&#x20;

* dbnl-generated alerts regarding highly correlated columns (in depth on a separate screen),
* Summary statistics for columns (along with shortcuts to [create tests](/v0.25.x/using-distributional/tests/creating-tests.md#context-driven-test-creation) for any statistics of note), and
* Notable behavior for columns, such as a skewed or multimodal distribution.

<figure><img src="/files/siQVTTySn8hedZWMIcgt" alt=""><figcaption><p>At the Run Detail page, you can gain quick insights regarding your app's behavior and add tests on those insights as you desire.</p></figcaption></figure>

## Compare page

At the top of the Run Detail page, there are links to the Compare and Analyze pages, where you can conduct more in depth and customized analysis. You can drive your own analysis at these pages to uncover key insights about your app.

For example, after seeing a failed Test Session in a RAG (Q & A) application, you may visit the Compare page to understand the impact of adding new documents to your vector database. The image below shows a sample Compare page, which reveals a sizable decrease in the population of poorly-retrieved questions (drop in the low bleu value between Baseline and Experiment).

<figure><img src="/files/eHJMfvzPK02ITFD3Khgj" alt=""><figcaption><p>The Compare Page exposes a significant drop in low-performing bleu scores when new documents are added to the vector database.</p></figcaption></figure>

[Filtering for those columns](/v0.25.x/to-be-deleted/using-filters/filters-in-the-compare-page.md) (the screenshot below) gives a valuable insight about the impact of the extra documents.  You see that, previously, the RAG app was incorrectly retrieving documents from “Liabilities and Contingencies” as well as “Asset Valuations.” Adding the new documents improved your app’s quality, and now you can confidently answer, “Yes, my app’s behavior has changed, and I am satisfied with its new behavior.”

<figure><img src="/files/1NlvJiGGskxbKl5fJDyg" alt=""><figcaption><p>Applying a filter for low bleu score values allows you to identify which documents are being better retrieved with the extra 100 documents in the vector database.</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.dbnl.com/v0.25.x/to-be-deleted/stages-in-the-ai-software-development-lifecycle/reviewing-test-sessions-and-runs-in-distributional/insights-surfaced-elsewhere-on-distributional.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.
