AWS appstream2 documentation change
Summary
Added detailed capacity metrics definitions for multi-session fleets
Security assessment
Change introduces operational monitoring metrics without security context or vulnerability mitigation
Diff
diff --git a/appstream2/latest/developerguide/usage-metrics-multi-session.md b/appstream2/latest/developerguide/usage-metrics-multi-session.md index 5c4a386e1..0d418a7c1 100644 --- a//appstream2/latest/developerguide/usage-metrics-multi-session.md +++ b//appstream2/latest/developerguide/usage-metrics-multi-session.md @@ -42,0 +43,46 @@ Monitoring this metric helps with decisions about increasing or decreasing the v +`ActualCapacity` | The total number of instances that are available for streaming or are currently streaming. For multi-session fleets, this metric represents instance-level capacity. The relationship between instance-level and session-level capacity is as follows: + + + ActualUserSessionCapacity = ActualCapacity × (Maximum number of user sessions per instance) + + + ActualCapacity = ActualUserSessionCapacity / (Maximum number of user sessions per instance) + +| [Fleet] | Average, Minimum, Maximum | Count +`DesiredCapacity` | The total number of instances that are either running or pending. This represents the total number of instances your fleet targets in a steady state. For multi-session fleets, the relationship between instance-level and session-level capacity is as follows: + + + DesiredUserSessionCapacity = DesiredCapacity × (Maximum number of user sessions per instance) + + + DesiredCapacity = DesiredUserSessionCapacity / (Maximum number of user sessions per instance) + +| [Fleet] | Average, Minimum, Maximum | Count +`InUseCapacity` | The number of instances currently being used for streaming sessions. For multi-session fleets, an instance is considered in use if it has at least one active user session. The relationship between instance-level and session-level capacity is as follows: + + + ActiveUserSessionCapacity = InUseCapacity × (Maximum number of user sessions per instance) + + + InUseCapacity = ActiveUserSessionCapacity / (Maximum number of user sessions per instance) + +| [Fleet] | Average, Minimum, Maximum | Count +`PendingCapacity` | The number of instances being provisioned by WorkSpaces Applications. Represents the additional number of instances the fleet will have after provisioning is complete. When provisioning starts, it usually takes 10-20 minutes for an instance to become available for streaming. For multi-session fleets, the relationship between instance-level and session-level capacity is as follows: + + + PendingUserSessionCapacity = PendingCapacity × (Maximum number of user sessions per instance) + + + PendingCapacity = PendingUserSessionCapacity / (Maximum number of user sessions per instance) + +| [Fleet] | Average, Minimum, Maximum | Count +`RunningCapacity` | The total number of instances currently running. Represents the number of instances that can support streaming sessions in the fleet's current state. For multi-session fleets, the relationship between instance-level and session-level capacity is as follows: + + + RunningUserSessionCapacity = RunningCapacity × (Maximum number of user sessions per instance) + + + RunningCapacity = RunningUserSessionCapacity / (Maximum number of user sessions per instance) + +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. This metric applies the same way for both single-session and multi-session fleets. You can set alarms to use this metric to be notified of users waiting for streaming sessions. | [Fleet] | Average, Minimum, Maximum, Sum | Count