> For the complete documentation index, see [llms.txt](https://docs.nuvens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvens.cloud/admin/admin-section/workspaces-applications-metrics.md).
# WorkSpaces Applications Metrics
Similar to WorkSpaces Personal to access process-level metrics, the **WSM Agent** and a **CloudWatch Log Group** are required.
{% hint style="warning" %}
The WSM Agent must be installed on the WorkSpaces Applications Fleet Image.
{% endhint %}
The **Details** tab displays key information about the selected user session, including the **Account** and **Region**, **Fleet** and **Stack**, **Instance**, **Instance Type**, **Image** and current **Connection State**. It also shows session timing information including when the session started, its maximum expiry time, end time, and recorded duration.
The **Graphs** tab provides a visual overview of performance metrics for the selected session over time. This includes **Session Latency**, **Bandwidth**, **Inbound Bandwidth**, and **TCP Retransmission Rate**, helping administrators identify connectivity or network performance issues experienced during the WorkSpaces Application session.
The **Stats** tab displays performance statistics for the selected session including **average CPU**, **average memory**, **root disk space**, and **user disk space**. It also provides recorded samples showing **CPU and memory usage**, **disk reads/writes**, and **network traffic**, helping administrators review resource utilisation during the session.
The **Activity** tab provides an overview of user activity during the selected session, showing the time spent **Active**, **Idle**, and **Disconnected**. A timeline displays when each activity state occurred throughout the session, while recorded **Agent Events** such as user logins are shown below to provide further insight into the user’s session activity.
The **App Usage** tab shows application activity for the selected session, including the total **Recorded foreground time** and number of **Applications used**.
Each application is listed with its **Time Used** and **Share of Foreground Time**, helping administrators understand which applications were used most during the session.
The **Costing** tab provides a breakdown of the estimated **session & user** **compute costs** associated with the selected user session. It displays the **recorded session hours**, **hourly compute rate**, and calculated **session cost**, along with the user’s total compute cost for the selected time period.
{% hint style="warning" %}
These figures represent recorded compute costs and may not reflect the final AWS bill. Excludes RDS user fees, discounts and unpriced sessions.
{% endhint %}
The **History** tab displays previous sessions for the selected user within the chosen time period, including the **session start time**, **Fleet and Stack** and **recorded session hours**. Click **Inspect** next to a session to view its associated **Details**, **Graphs**, **Stats**, **Activity**, and **Costing** information.
---
# 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://docs.nuvens.cloud/admin/admin-section/workspaces-applications-metrics.md?ask=&goal=
```
`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.
