# Data Analysis

This view is useful when you want to analyze your collected method invocations. There are only two fields that need to be fill out. You must specify both the date range and the application. Then, the analysis will be performed for those method invocations which ended within the specified time range and came from the specified application. 

<figure><img src="https://3067115593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ocNRvfTUINtskO6osm1%2Fuploads%2FaG4c6ryiztrqcL0HWpOl%2FScreenshot%202023-11-02%20at%2012.11.50.png?alt=media&#x26;token=cf1993e3-f8d5-4020-b3d2-e4bc7e41173e" alt=""><figcaption><p>Data Analysis Form</p></figcaption></figure>

## Duration Distribution

The first part of the analysis presents the methods duration distribution with respect to percentiles. The chart below presents a sample analysis result. The analysis is performed for all methods invocations within the time range specified in the data analysis form.

<figure><img src="https://3067115593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ocNRvfTUINtskO6osm1%2Fuploads%2FxZrSN1JMD9X8mxs3CaMI%2FScreenshot%202023-11-02%20at%2012.13.24.png?alt=media&#x26;token=186d8ba8-03bd-45c7-91b1-77f812d6a556" alt=""><figcaption><p>Sample Duration Distribution</p></figcaption></figure>

The chart is divided into percentile sections. The percentile values are located on the `x`-axis. The left `y`-axis presents the method duration value, while the right one the number of method invocations. Each percentile section has a <mark style="color:green;">bar</mark> which represents the number of method invocations within the percentile interval. The blue <mark style="color:blue;">curve</mark> represents the methods duration.&#x20;

To properly read the chart, you need to focus on the percentile axis (`x`-axis). Note, the `x`-axis is not scaled linearly. Suppose now, we have the analysis results as the one above in the picture. We interpret the chart at `75th` percentile as follows:

* `75` percent of all invocations execute below `10` ms.&#x20;
* there are `5524` invocations whose duration is between `5` and `10` ms.
* there are also `841` invocations with exceptions.

Note, `5` ms is taken from the previous percentile, which is `50` in this case.&#x20;

It is easy to see, in the sample case, that the number of methods invocations decreases rapidly as percentile grows. There are only a few outliers, whose duration is above a minute. It is up to a user whether a further analysis is required or not. If a more detailed investigation is needed a user can proceed with the analysis by pressing the <mark style="color:blue;">`Temporal analysis`</mark> button.

## Temporal Analysis

This part of the analysis presents how the percentile values change in time for the specified period. There are two tabs with the results. The first one <mark style="color:blue;">`Values`</mark> presents how the percentile values change in time. Just like in the duration distribution there are bars and curves. The bars represent the amounts of invocations in time periods. The curves present the percentile values of duration. There are four percentiles curves that can be displayed simultaneously, i.e. 25th, 50th, 75th and 9\*th. The last one is customizable and can be changed in the <mark style="color:blue;">`Highest percentile`</mark> option.

<figure><img src="https://3067115593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ocNRvfTUINtskO6osm1%2Fuploads%2FGHuafCKjfkJB1u6Qv2tO%2FScreenshot%202023-11-02%20at%2012.14.28.png?alt=media&#x26;token=6861d2fa-d22f-459d-b990-e05136696478" alt=""><figcaption><p>Sample Temporal Analysis</p></figcaption></figure>

## 2D Analysis

The 2D analysis is represented in a form of a heatmap chart. The chart presents a distribution of one of the selected <mark style="color:blue;">`Data type`</mark> with respect to both duration (vertical axis) and time (horizontal axis). The chart is divided into cells, which aggregate data for particular ranges of duration and time. For <mark style="color:blue;">`Count`</mark> data type, each cell represents a number of invocations within the cell range. For <mark style="color:blue;">`Off-Cpu`</mark> data type, each cell represents a percentage of method invocations, whose off-cpu time is the largest. For <mark style="color:blue;">`Exceptions`</mark> data type, each cell represents a number of methods that throw exceptions. &#x20;

<figure><img src="https://3067115593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ocNRvfTUINtskO6osm1%2Fuploads%2FsGA2cA4opdVYUxo3L2Zc%2FScreenshot%202023-11-02%20at%2012.15.37.png?alt=media&#x26;token=b3259d46-3e6c-4c99-aca8-beee1420ff78" alt=""><figcaption><p>Sample 2D Analysis</p></figcaption></figure>

You can change the number of cells the chart is divided into, by selecting one of the <mark style="color:blue;">`Resolution`</mark> value. You can also change the range of methods that are analyzed by selecting one of the <mark style="color:blue;">`Precentile`</mark> values. For example, if the <mark style="color:blue;">`Percentile`</mark> value is 50, it means that the chart shows only those method invocations whose duration value is below the value at 50th percentile.&#x20;

## Exceptions

This view presents top ten [root exceptions](https://docs.flopsar.com/5.2/glossary#execution-stack) thrown by methods.

<figure><img src="https://3067115593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ocNRvfTUINtskO6osm1%2Fuploads%2FjtgeMReqzquafAVsbfAU%2FScreenshot%202023-11-02%20at%2012.16.45.png?alt=media&#x26;token=aefe1224-f5cb-4d34-abf6-0ff2cd73153f" alt=""><figcaption></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.flopsar.com/5.2/user-guide/data-analysis.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.