> For the complete documentation index, see [llms.txt](https://astro-rpa.gitbook.io/astro-rpa-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://astro-rpa.gitbook.io/astro-rpa-user-guide/astro-studio/capturetraffic.md).

# Traffic record

The Astro Studio traffic tracking subsystem allows you quickly and easily analyzing the exchange with portals, sites and web services, as well as generating Web requests in scripts based on the data received.

The tracking subsystem is represented by the Traffic Capture, Packet Properties and Traffic Filter panels.

![](/files/Z5yVjpRwyrDmzx9ipZJQ)

The Traffic Capture panel displays, in chronological order, all requests and responses occurring at the user's workplace in real time. To start recording the traffic, you should click the Start capturing button ![](/files/yXg8VMQv9anQRLS7R1lH). As soon as you click the button, the panel table will start to display the requests made from your workplace. The table of requests (queries) displays the following data:

* Result: Request event code
* Protocol: Request protocol type
* Host: Host name
* URL: Remote machine address
* Body: Request (query) body size in bytes
* Caching: Information on caching
* Type of content

Request and response body text can be found by clicking on the + icon in the request header

![](/files/swu5ALDdz21bR49aUX1D)

To stop recording click the Stop Interception button ![](/files/5BFOXHSE2sKl8WZYbTQ3)

To delete selected requests from the list, click the Delete button ![](/files/CdXG8lNd3pRZN0Qucc9r)

To clear the list of requests, click the Clear button ![](/files/g0OHGZGlkUMR5cuXDZxA)

To get more information about a request and a response, you need to select it in the Traffic Capture panel, and then the information about the request will be reflected in the Properties panel of the packet.

![](/files/UhAhqkAsHsPkB4FXllrI)

There is information about requests in the upper part of the panel. There is information about responses in the lower part of the panel. The information contained in the panel is divided into the following categories:

* Headers: Information on headers
* Text: Request body text
* Clear: Request/response text in clear text (headers and body)
* JSON: Body data view in the form of JSON
* XML: XML review of body data

There is the Traffic Filter panel necessary for pre-filtering traffic.

![](/files/OKFw2yMmwuslBv3VMaZ0)

This panel allows:

* Enabling tracking of CONNECT type requests
* Enabling interception of multimedia content requests
* Creating special filters

In the special filter table, you can create filters for certain elements of a request/response based on regular expressions. The filter contains the following elements:

* Result
* Protocol
* Host
* URL
* Content type (request)
* Content type (response)
* Header (request)
* Header (response)
* Body (request)
* Body (response)

For example, to filter requests only to sites with a URL including mail, you need to create a filter with the URL Object and the Expression.\*mail.\*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://astro-rpa.gitbook.io/astro-rpa-user-guide/astro-studio/capturetraffic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.