> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-mp-guide/v19-en-us/appendix/ras-performance-counters.md).

# RAS performance counters

The following table lists performance counters available in Parallels RAS per component:

## **Parallels RAS Gateway (2XProxyGateway.exe)**

| ID                     | Name                           | Description                                                        |
| ---------------------- | ------------------------------ | ------------------------------------------------------------------ |
| ras\_gw\_tot\_conn     | Total connections              | The total number of Connections with the Gateway.                  |
| ras\_gw\_tot\_threads  | Total threads                  | The total number of threads running on the Gateway.                |
| ras\_gw\_rpd\_sess     | RDP tunneled sessions          | The number of tunneled RDP sessions.                               |
| ras\_gw\_rpd\_sess\_s  | RDP SSL tunneled sessions      | The number of tunneled RDP sessions over SSL.                      |
| ras\_gw\_html          | HTTP connections               | The number of tunneled HTTP sockets                                |
| ras\_gw\_html\_s       | HTTPS connections              | The number of tunneled HTTPS sockets                               |
| ras\_gw\_html5         | HTML5 connections              | The number of tunneled HTTP5 sockets                               |
| ras\_gw\_html5\_s      | HTML5 SSL connections          | The number of tunneled HTTP5 sockets over SSL                      |
| ras\_gw\_cm            | Device Manager connections     | The number of Parallels Device Manager connections                 |
| ras\_gw\_cm\_s         | Device Manager SSL connections | The number of Parallels Device Manager connections over SSL        |
| ras\_gw\_wyse          | Wyse connections               | The number of Wyse connections                                     |
| ras\_gw\_wyse\_s       | Wyse SSL connections           | The number of Wyse connections over SSL                            |
| ras\_gw\_rdpudp        | RDP UDP tunneled sessions      | The number of RDP UDP connections                                  |
| ras\_gw\_rdpudp\_s     | RDP UDP DTLS tunneled sessions | The number of RDP UDP connections over DTLS                        |
| ras\_gw\_cache\_sock   | Cached sockets                 | The number of cached sockets between Gateway and Connection Broker |
| ras\_gw\_idle\_threads | Idle threads                   | The number of idle threads on the Gateway                          |
| ras\_gw\_client        | Client connections             | The number of Parallels Client connections                         |
| ras\_gw\_client\_s     | Client SSL connections         | The number of Parallels Client connections over SSL                |

## **Parallels RAS Connection Broker (2XController.exe)**

| ID                                     | Name                                            | Description                                                     |
| -------------------------------------- | ----------------------------------------------- | --------------------------------------------------------------- |
| ras\_pa\_avg\_client\_connection\_time | Average time for client connection              | The average client connection time.                             |
| ras\_pa\_avg\_client\_auth\_time       | Average time for user authentication            | The average time taken to authenticate a user.                  |
| ras\_pa\_avg\_client\_policy\_time     | Average time to retrieve user policy            | The average time taken to retrieve the user's policy.           |
| ras\_pa\_avg\_client\_rep\_time        | Average time to send client telemetry           | The average time taken to send client telemetry. Used by CEP.   |
| ras\_pa\_avg\_client\_applist\_time    | Average time to retrieve user's published items | The average time taken to retrieve user's published items list. |
| ras\_pa\_avg\_client\_appicons\_time   | Average time to retrieve icons                  | The average time taken to retrieve published items icons.       |
| ras\_pa\_avg\_client\_getidle\_time    | Average time to start up a request              | The average time taken for the start up request.                |

## **Parallels RAS RDS Agent (2XAgent.exe)**

| ID         | Name                      | Description                              |
| ---------- | ------------------------- | ---------------------------------------- |
| act\_sess  | Active RDS sessions       | The number of active RDS Sessions.       |
| disc\_sess | Disconnected RDS sessions | The number of disconnected RDS Sessions. |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-mp-guide/v19-en-us/appendix/ras-performance-counters.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.