# Data Browsing

Workstation allows you to browse all the collected data. In order to browse the data, you need to fill out the form below.

![Data Browser Form](/files/-LwNxVsKh4CzzAs0jT2_)

You must specify at least a pattern for agents and the time range. Additionally, you can search for methods by parameters. In `KEY` field, you must specify an exact key name for the parameters. In `VALUE` field, you must specify a phrase to search for. How the phrase will be matched depends on the option selected below the field. If you select `contains` option, only those methods will be returned, which parameters value contain the phrase. If you select `exact` option, only those methods will be returned, which parameters value equal to the phrase. Finally, if you select `regex` option, the phrase will be regarded as a regular expression and only those methods will be returned, which parameters value match the regular expression. 

By default, the parameters are searched only for root calls. If you want to search for parameters in every method call of the root call execution stack, then you need to select `DEEP SEARCH` option.

## Browse Result View

When you click `SEARCH` button, you will get a similar view to the one below.

![Exemplary Browse Data Result](/files/-Ly97BVGVk3PhNe1A2Dz)

The table is composed of the following columns:

* `AGENT` : name and type of the agent,
* `THREAD` : name of the thread the call was executed within,
* `METHOD` : method name and signature,
* `PARAMETERS` : method parameters preview,
* `TIME` : time stamp of the end of the method execution,
* `EXCS INSIDE` : number of exceptions thrown within the method execution tree,
* `CPU TIME` : percentage of duration the method spent on CPU,
* `DURATION` : method execution duration,
* `CALLS` : total number of reported methods execution within the method execution tree.

Whenever you click a record in the table, the details of the selected method are displayed on the right panel. The details cover:

* `CLASS` : fully qualified class name the selected method is member of,
* `METHOD` : method name and signature,
* `TIME` : time stamp of the end of the method execution,
* `DURATION`: method execution duration,
* `CPU TIME` : time the method spent on CPU,

You can see any [record details](/3.0/user-guide/execution-stack-interpretation.md) by double clicking it. 

### Parameters List

Additionally, when the selected method has parameters, they are displayed in the `PARAMETERS` list. The list records contain both `KEY` and `VALUE`. When you select a list record, its value is displayed in the text area below the list. 

The list has a context menu, which contains several actions you can perform on a selected parameter.

![Parameters List Context Menu](/files/-LzqkqMzF7foK68sqLNq)

| Menu Item        | Description                                                                                                                                                                                                    |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| *Search similar* | Use this action if you want to search for method calls, which have a similar value to the selected parameter. This action will bring up the Data Browser form, prefilled with the agent and parameters fields. |
| *Reformat*       | Use this action to format the selected parameter value in the text area view. You need to specify a separator, which will be used to break lines in the text area.                                             |


---

# 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/3.0/user-guide/data-browsing.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.