# Monitoring Amazon WorkSpaces Applications Resources
WorkSpaces Applications publishes metrics to Amazon CloudWatch to enabled detailed tracking and deep dive analysis. These statistics are recorded for an extended period so you can access historical information and gain a better perspective on how your fleets are performing. For more information, see the [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/).
**Topics**
+ [Viewing Fleet Usage Using the Console](monitoring-console.md)
+ [Viewing Instance and Session Performance Metrics Using the Console](monitoring-instance-session-performance.md)
+ [WorkSpaces Applications Metrics and Dimensions](monitoring-with-cloudwatch.md)
+ [Manage Multi-Session Fleet Instances](manage-multi-session-instances.md)
+ [Create custom CloudWatch dashboards using CloudFormation templates](custom-cloudwatch-dashboards.md)
+ [Monitor your WorkSpaces Applications health using the CloudWatch automatic dashboard](cloudwatch-automatic-dashboard.md)
# Viewing Fleet Usage Using the Console
You can monitor your Amazon WorkSpaces Applications fleet usage using the WorkSpaces Applications or CloudWatch console.
**To view fleet usage in the WorkSpaces Applications console**
1. Open the WorkSpaces Applications console at [https://console.aws.amazon.com/appstream2/home](https://console.aws.amazon.com/appstream2/home).
1. In the left pane, choose **Fleets**.
1. Select a fleet and choose its **Fleet Usage** tab.
1. By default, the graph displays the following metrics:
+ `ActualCapacity`, `InUseCapacity`, `DesiredCapacity`, `AvailableCapacity`, `PendingCapacity`, and `CapacityUtilization` for single-session fleets.
+ `ActualUserSessionCapacity`, `ActiveUserSessionCapacity`, `AvailableUserSessionCapacity`, `DesiredUserSessionCapacity`, `PendingUserSessionCapacity`, `CapacityUtilization`, `DrainingCapacity`, `DrainModeActiveUserSessionCapacity`, and `DrainModeUnusedUserSessionCapacity` for multi-session fleets.
**To view fleet usage in the CloudWatch console**
1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).
1. In the left pane, choose **Metrics**.
1. Choose the **AppStream** namespace and then choose **Fleet Metrics**.
1. Select the metrics to graph.
# Viewing Instance and Session Performance Metrics Using the Console
You can monitor Amazon WorkSpaces Applications fleet instances and session performance using the WorkSpaces Applications console or the CloudWatch console.
Performance metrics are collected at a 5-minute interval. After a new session is provisioned, the first metric data point will show up in 5 minutes. Subsequent metric data points will be available at every 5-minute interval.
**Note**
Performance metrics are currently available only for multi-session fleets
**To view instance and session in the WorkSpaces Applications console**
1. Open the WorkSpaces Applications console at [https://console.aws.amazon.com/appstream2/home](https://console.aws.amazon.com/appstream2/home).
1. In the left pane, choose **Fleets**.
1. Select a fleet and choose **View Details** and **View Sessions**.
1. Select a session to view the metrics.
1. By default, the graph displays the following metrics:
+ Instance metrics
+ CpuUtilizationInstance
+ MemoryUtilizationInstance
+ PagingFileUtilizationInstance
+ DiskUtilizationInstance
+ Session metrics
+ CpuUtilizationSession
+ MemoryUtilizationSession
**To view instance and session performance in the CloudWatch console**
1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).
1. In the left pane, choose **Metrics**.
1. Choose the **AppStream** namespace and then choose **Fleet Instance Metrics** or **Fleet Session Metrics**.
1. Select the metrics to graph.
# WorkSpaces Applications Metrics and Dimensions
Amazon WorkSpaces Applications sends the following metrics and dimension information to Amazon CloudWatch.
All of the following metrics except `InsufficientConcurrencyLimitError` apply to Always-On and On-Demand fleets. The only metrics that apply to Elastic fleets are `InUseCapacity` and `InsufficientCapacityError`.
WorkSpaces Applications sends metrics to CloudWatch one time every minute. The `AWS/AppStream` namespace includes the following metrics.
**Topics**
+ [Fleet Usage Metrics for Single-session Fleets](appstream-dimensions.md)
+ [Fleet Usage Metrics for Multi-session Fleets](usage-metrics-multi-session.md)
+ [Instance and Session Performance Metrics for Single-session and Multi-session Fleets](instance-session-metrics-single-session-multi-session.md)
+ [Dimensions for Amazon WorkSpaces Applications Metrics](dimensions-metrics.md)
# Fleet Usage Metrics for Single-session Fleets
The following are fleet usage metrics for single-session fleets.
| Metric | Description | Dimensions | Statistics | Units |
| --- | --- | --- | --- | --- |
| ActualCapacity | The total number of instances that are available for streaming or are currently streaming. ActualCapacity = AvailableCapacity + InUseCapacity
| [Fleet] | Average, Minimum, Maximum | Count |
| AvailableCapacity | The number of idle instances currently available for user sessions. AvailableCapacity = ActualCapacity - InUseCapacity
| [Fleet] | Average, Minimum, Maximum | Count |
| CapacityUtilization | The percentage of instances in a fleet that are being used, using the following formula. CapacityUtilization = (InUseCapacity/ActualCapacity) * 100
Monitoring this metric helps with decisions about increasing or decreasing the value of a fleet's desired capacity. | [Fleet] | Average, Minimum, Maximum | Percent |
| DesiredCapacity | The total number of instances that are either running or pending. This represents the total number of concurrent streaming sessions your fleet can support in a steady state. DesiredCapacity = ActualCapacity + PendingCapacity
| [Fleet] | Average, Minimum, Maximum | Count |
| InUseCapacity | The number of instances currently being used for streaming sessions. One `InUseCapacity` count represents one streaming session. | [Fleet] | Average, Minimum, Maximum | Count |
| PendingCapacity | The number of instances being provisioned by WorkSpaces Applications. Represents the additional number of streaming sessions the fleet can support after provisioning is complete. When provisioning starts, it usually takes 10-20 minutes for an instance to become available for streaming. | [Fleet] | Average, Minimum, Maximum | Count |
| RunningCapacity | The total number of instances currently running. Represents the number of concurrent streaming sessions that can be supported by the fleet in its current state. This metric is provided for Always-On fleets only, and has the same value as the `ActualCapacity` metric. | [Fleet] | Average, Minimum, Maximum | Count |
| InsufficientCapacityError | The number of session requests rejected due to lack of capacity. You can set alarms to use this metric to be notified of users waiting for streaming sessions. | [Fleet] | Average, Minimum, Maximum, Sum | Count |
| InsufficientConcurrencyLimitError | The number of Elastic fleet session requests rejected due to reaching max concurrent streaming capacity. You can set alarms to use this metric to be notified of users waiting for streaming sessions. | [Fleet] | Average, Minimum, Maximum, Sum | Count |
# Fleet Usage Metrics for Multi-session Fleets
The following are fleet usage metrics for multi-session fleets.
| Metric | Description | Dimensions | Statistics | Units |
| --- | --- | --- | --- | --- |
| CapacityUtilization | The percentage of sessions in a fleet that are being used, using the following formula. CapacityUtilization = (ActiveUserSessionCapacity / ActualUserSessionCapacity) * 100
Monitoring this metric helps with decisions about increasing or decreasing the value of a fleet's desired capacity. | [Fleet] | Average, Minimum, Maximum | Percent |
| ActualUserSessionCapacity | The total number of session slots that are available for streaming or are currently streaming. ActualUserSessionCapacity = AvailableUserSessionCapacity + ActiveUserSessionCapacity
| [Fleet] | Average, Minimum, Maximum | Count |
| AvailableUserSessionCapacity | The number of idle session slots currently available for user sessions. AvailableUserSessionCapacity = ActualUserSessionCapacity - ActiveUserSessions
| [Fleet] | Average, Minimum, Maximum | Count |
| DesiredUserSessionCapacity | The total number of session slots that are either running or pending. This represents the total number of concurrent streaming sessions your fleet can support in a steady state. DesiredUserSessionCapacity = ActualUserSessionCapacity + PendingUserSessionCapacity
| [Fleet] | Average, Minimum, Maximum | Count |
| ActiveUserSessionCapacity | The number of user sessions currently being used for streaming sessions. | [Fleet] | Average, Minimum, Maximum | Count |
| PendingUserSessionCapacity | The number of session slots being provisioned by WorkSpaces Applications. Represents the additional number of streaming sessions the fleet can support after provisioning is complete. When provisioning starts, it usually takes 10-20 minutes for an instance to become available for streaming. | [Fleet] | Average, Minimum, Maximum | Count |
| RunningUserSessionCapacity | The total number of session slots currently that are available for streaming or are currently streaming. Represents the number of concurrent streaming sessions that can be supported by the fleet in its current state. This metric is provided for Always-On fleets only, and has the same value as the `ActualUserSessionCapacity` metric. | [Fleet] | Average, Minimum, Maximum | Count |
| DrainingCapacity | The number of instances in Drain Mode. | [Fleet] | Average, Minimum, Maximum | Count |
| DrainModeActiveUserSessionCapacity | The number of active user sessions on instances in Drain Mode. | [Fleet] | Average, Minimum, Maximum | Count |
| DrainModeUnusedUserSessionCapacity | The number of unused session slots on instances in Drain Mode which cannot be used for user session provisioning. | [Fleet] | Average, Minimum, Maximum | Count |
# Instance and Session Performance Metrics for Single-session and Multi-session Fleets
The following are instance and session performance metrics for single-session and multi-session fleets.
| Metric | Description | Dimensions | Statistics | Units |
| --- | --- | --- | --- | --- |
| CpuUtilizationInstance | The percentage of allocated compute units that are currently in use on the instance. | [Fleet] [UserId] [FleetName, InstanceId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Percent |
| MemoryUtilizationInstance | The percentage of allocated physical memory units that are currently in use on the instance. | [Fleet] [UserId] [FleetName, InstanceId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Percent |
| PagingFileUtilizationInstance | The percentage of the paging file that is currently in use to extend the Memory (RAM) capacity. | [Fleet] [UserId] [FleetName, InstanceId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Percent |
| DiskUtilizationInstance | The percentage of disk units that are currently in use to run programs and carry out tasks on the instance. | [Fleet] [UserId] [FleetName, InstanceId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Percent |
| CpuUtilizationSession | The percentage of allocated compute units that are currently in use by the session. | [Fleet] [UserId] [FleetName, InstanceId, SessionId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Percent |
| MemoryUtilizationSession | The percentage of allocated physical memory units that are currently in use by the session. | [Fleet] [UserId] [FleetName, InstanceId, SessionId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Percent |
| DiskReadOperations | Amount of disk reads per instance | [Fleet] [UserId] [FleetName, InstanceId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Count |
| DiskWriteOperations | Amount of disk write per instance | [Fleet] [UserId] [FleetName, InstanceId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Count |
| InSessionLatency | Round trip time between WorkSpaces Application server and client measured at p90 | [Fleet] [UserId] [FleetName, InstanceId, SessionId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Milliseconds |
| FramesPerSecond | Frames per second for the specific session | [Fleet] [UserId] [FleetName, InstanceId, SessionId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Count |
| Bandwidth | Amount of data transferred between WorkSpaces Applications service and Client during the session. | [Fleet] [UserId] [FleetName, InstanceId, SessionId] [FleetName, InstanceId, SessionId, UserId] | Average, Minimum, Maximum | Kilobits/Second |
# Dimensions for Amazon WorkSpaces Applications Metrics
The `AWS/AppStream` namespace includes the following dimensions and dimension groups.
| Dimension | Description |
| --- | --- |
| Fleet | Filters the metric data by name of the Fleet. |
| FleetName | Filters the metric data by name of the Fleet. |
| SessionId | Filters the metric data by session identifier. |
| InstanceId | Filters the metric data by instance identifier. |
| UserId | Filters the metric data by user identifier. |
| Dimension | Where Available in Amazon CloudWatch Metrics |
| --- | --- |
| [Fleet] | Fleet Metrics |
| [FleetName, InstanceId] | Fleet Instance Metrics |
| [FleetName, InstanceId, SessionId] | Fleet Session Metrics |
| [UserId] | UserId |
| [FleetName, InstanceId, SessionId, UserId] | FleetName, InstanceId, SessionId, UserId |
# Manage Multi-Session Fleet Instances
When running multi-session fleets on Amazon WorkSpaces Applications, multiple user sessions share a fleet instance. Unlike single-session fleets — where each instance serves one user and is automatically recycled after the session is terminated — multi-session instances can remain active for extended periods as long as users continue to occupy sessions on them.
This creates an important operational consideration: a multi-session instance cannot be terminated while active user sessions are running. If an instance is never fully vacated, it may never be reclaimed or rebooted, which means:
+ **Image updates may not propagate** — new image versions containing patches, software updates, or security fixes will not reach an instance until all sessions on it have ended and the instance is recycled.
+ **Fleet hygiene is harder to maintain** — without a mechanism to gracefully cycle instances, administrators must manually restart fleets or terminate all active sessions to apply updates, which can be disruptive to end users.
+ **Long-running instances may experience performance degradation** — instances that remain active for extended periods without a restart can accumulate resource contention, memory pressure, and other system-level issues over time, leading to a degraded experience for end users sharing that instance.
To address this, WorkSpaces Applications provides a method to manage the lifecycle of individual fleet instances through a process called draining (also referred to as Drain Mode).
Putting an instance in Drain Mode impacts the capacity of the fleet. The fleet capacity metrics are available at [Viewing Fleet Usage Using the Console](monitoring-console.md).
# Drain a Fleet Instance
Draining an instance means instructing the fleet to stop accepting new user sessions while allowing existing sessions to continue until users naturally disconnect. Once all sessions have ended, the instance is automatically reclaimed and replaced with a fresh instance running the latest image.
This approach lets you:
+ **Apply image updates without disrupting users** — existing sessions run to completion, while new sessions are routed to other instances.
+ **Manage maximum instance lifetime** — by periodically draining older instances, you ensure that no instance runs indefinitely without being refreshed.
+ **Maintain fleet hygiene proactively** — rather than waiting for a full fleet restart, you can cycle individual instances on a rolling basis.
**Note**
Draining an instance does not disconnect or terminate active user sessions. Users already connected will not be affected.
**Important**
Once an instance is placed in Drain Mode, this action cannot be reversed. The instance will continue to drain until all active sessions have ended and it is reclaimed.
# When to Drain an Instance
Consider draining a fleet instance when:
+ A new image version has been published and you want to roll it out without a full fleet restart.
+ An instance has been running for an extended period and you want to refresh it.
+ You observe performance degradation on sessions running on a specific instance and want to recycle it without terminating active sessions.
# How to Drain an Instance
1. Open the WorkSpaces Applications console at [https://console.aws.amazon.com/appstream2/home](https://console.aws.amazon.com/appstream2/home).
1. In the left pane, choose **Fleets**.
1. Select a multi-session fleet and choose **View Details** and **View Sessions**.
1. Select a session running on the instance you want to drain.
1. Choose **Drain Session Instance**.
The instance will immediately stop accepting new sessions. Existing sessions will continue uninterrupted. Once the last session ends, the instance is automatically terminated and replaced.
# Create custom CloudWatch dashboards using CloudFormation templates
AWS provides CloudFormation templates that you can use to create custom CloudWatch dashboards for WorkSpaces Applications. Choose from the following CloudFormation template options to create custom dashboards for your WorkSpaces Applications workloads in the CloudFormation console.
**Considerations before getting started**
Consider the following before you get started with custom CloudWatch dashboards:
+ Create your dashboards in the same AWS Region as the deployed WorkSpaces you want to monitor.
+ You can also create custom dashboards using the CloudWatch console.
+ A cost might be associated with custom CloudWatch dashboards. For information about pricing, see [Amazon CloudWatch Pricing](https://aws.amazon.com/cloudwatch/pricing/).
**Prerequisites**
Before you begin, ensure you have access to the AWS Management Console and appropriate permissions to create CloudFormation stacks and CloudWatch dashboards.
**Procedure**
This procedure covers three CloudFormation templates for monitoring WorkSpaces Applications fleets: the Fleet Dashboard for fleet-level health metrics with drill-down capabilities, the User Dashboard for individual user session experience troubleshooting, and the Fleet Performance Alerts template for automated email notifications when performance thresholds are breached.
**Fleet Dashboard Template**
The Fleet Dashboard gives administrators a drill-down view of a specific fleet's health. A Fleet dropdown at the top auto-populates with all fleets in the account, shows metrics for each fleet and instances associated to that fleet.
**Steps to create:**
1. [Open the Create Stack page in the CloudFormation console.](https://console.aws.amazon.com/cloudformation/home#/stacks/new?stackName=WorkSpacesApps-FleetDashboard&templateURL=https://cfn-templates-global-prod-iad.s3.us-east-1.amazonaws.com/cfn-templates/ws_apps_fleet_dashboard.yaml) This link opens the page with the Amazon S3 bucket location of the custom CloudWatch dashboard template pre-populated.
1. Review the default selections on the **Create stack** page, and choose **Next**.
1. On the **Specify stack details** page, do the following:
1. In the **Stack name** field, use the default name or enter a custom name for your stack.
1. In the **DashboardName** field, use the default name or enter a custom name for your dashboard.
1. Choose **Next**.
1. On the **Configure stack options** page, review the default selections, and choose **Next**.
1. On the **Review** page, scroll down to the **Transforms** section and select the acknowledgement checkboxes to confirm that CloudFormation might create IAM resources.
1. Choose **Submit** to create the stack and the custom CloudWatch dashboard.
1. After the stack creation is complete, open the CloudWatch console to view your newly created custom dashboard.
1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).
1. In the left navigation bar, choose **Dashboards**.
1. Under **Custom Dashboards**, choose the dashboard with the dashboard name you entered earlier in this procedure.
**User Dashboard Template**
The User Dashboard allows administrators to troubleshoot individual user experience. A UserId dropdown at the top auto-populates with all user IDs from CloudWatch metrics, shows metrics for each User.
**Steps to create:**
1. [Open the Create Stack page in the CloudFormation console.](https://console.aws.amazon.com/cloudformation/home#/stacks/new?stackName=WorkSpacesApps-UserDashboard&templateURL=https://cfn-templates-global-prod-iad.s3.us-east-1.amazonaws.com/cfn-templates/ws_apps_user_dashboard.yaml) This link opens the page with the Amazon S3 bucket location of the custom CloudWatch dashboard template pre-populated.
1. Review the default selections on the **Create stack** page, and choose **Next**.
1. On the **Specify stack details** page, do the following:
1. In the **Stack name** field, use the default name or enter a custom name for your stack.
1. In the **DashboardName** field, use the default name or enter a custom name for your dashboard.
1. Choose **Next**.
1. On the **Configure stack options** page, review the default selections, and choose **Next**.
1. On the **Review** page, scroll down to the **Transforms** section and select the acknowledgement checkboxes to confirm that CloudFormation might create IAM resources.
1. Choose **Submit** to create the stack and the custom CloudWatch dashboard.
1. After the stack creation is complete, open the CloudWatch console to view your newly created custom dashboard.
1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).
1. In the left navigation bar, choose **Dashboards**.
1. Under **Custom Dashboards**, choose the dashboard with the dashboard name you entered earlier in this procedure.
**Fleet Performance Alerts Template**
This template creates 6 CloudWatch alarms for a specific fleet and an Amazon SNS topic that sends email notifications when alarms trigger or recover. After deployment, the administrator will receive a confirmation email from Amazon SNS — they must confirm the subscription to start receiving alerts.
**Steps to create:**
1. [Open the Create Stack page in the CloudFormation console.](https://console.aws.amazon.com/cloudformation/home#/stacks/new?stackName=WorkSpacesApps-FleetAlarms&templateURL=https://cfn-templates-global-prod-iad.s3.us-east-1.amazonaws.com/cfn-templates/ws_apps_fleet_level_alarms_template.yaml) This link opens the page with the Amazon S3 bucket location of the custom CloudWatch dashboard template pre-populated.
1. Review the default selections on the **Create stack** page, and choose **Next**.
1. On the **Specify stack details** page, do the following:
1. In the **Stack name** field, use the default name or enter a custom name for your stack.
1. In the **FleetName** field, enter the Fleet name that you want alerting for.
1. In the **NotificationEmail** field, enter an email address through which you want to get notified.
1. Choose **Next**.
1. On the **Configure stack options** page, review the default selections, and choose **Next**.
1. On the **Review** page, scroll down to the **Transforms** section and select the acknowledgement checkboxes to confirm that CloudFormation might create IAM resources.
1. Choose **Submit** to create the stack and the custom CloudWatch dashboard.
1. After the stack creation is complete, open the CloudWatch console to view your newly created custom dashboard.
1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).
1. In the left navigation bar, choose **Dashboards**.
1. Under **Custom Dashboards**, choose the dashboard with the dashboard name you entered earlier in this procedure.
**Next steps**
After creating your dashboard, you can customize it further by adding or removing widgets, adjusting time ranges, and configuring alarms as needed.
# Monitor your WorkSpaces Applications health using the CloudWatch automatic dashboard
You can monitor WorkSpaces Applications using the CloudWatch automatic dashboard, which collects raw data and processes it into readable, near real-time metrics. The metrics are kept for 15 months to access historical information and to monitor the performance of your fleets, instances, and sessions. You can also set alarms that watch for certain thresholds, and send notifications or take actions when those thresholds are met. For more information, see the [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/).
The CloudWatch automatic dashboard is created when you use your AWS account to configure your WorkSpaces Applications. The dashboard allows you to monitor your WorkSpaces Applications metrics across Regions, including:
+ **Capacity metrics** — Monitor overall fleet capacity status, including capacity utilization, actual capacity, available capacity, desired capacity, in-use capacity, pending capacity, and running capacity. Track insufficient capacity errors to identify scaling issues.
+ **Performance metrics** — View fleet, instance, and session performance data including CPU utilization, memory utilization, disk utilization, paging file utilization, and disk I/O operations.
+ **Session quality metrics** — Monitor in-session latency, frames per second (FPS), and bandwidth to assess streaming performance and user experience.
You can use the dashboard for the following purposes:
+ Identify fleets experiencing capacity constraints or insufficient capacity errors.
+ Monitor resource utilization (CPU, memory, disk) over time to optimize instance sizing.
+ Track session quality metrics to identify performance degradation or network issues.
+ Identify anomalies to help with troubleshooting streaming or connectivity problems.
+ View metrics by fleet to compare performance across different configurations.
The automatic dashboard provides time range filters (1 hour, 3 hours, 12 hours, 1 day, 1 week, or custom) and displays metrics in UTC timezone by default.
**To use the WorkSpaces Applications CloudWatch automatic dashboard**
1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).
1. In the navigation pane, choose **Dashboards**.
1. Choose the **Automatic dashboards** tab.
1. Choose **AppStream**.