Help Docs

Amazon AppStream 2.0 Monitoring Integration

Amazon AppStream 2.0 is a fully managed non-persistent desktop and application service for remotely accessing your work. Monitor AppStream metrics, configure thresholds for key metrics, and automate incident remediation for seamless remote access.

In this doc, we'll cover:

Setup and configuration

  1. Log in to your Site24x7 account and create Site24x7 as an IAM user, or create a cross-account IAM role to enable access to your AWS resources for Site24x7.
  2. On the Integrate AWS Account page, check the box next to AppStream 2.0 in the Services to be discovered field.

Policies and permissions

Ensure the following read-level actions are present in the policy assigned to the Site24x7 IAM entity:

  • "appstream:DescribeFleets"
  • "appstream:ListAssociatedStacks"
  • "appstream:DescribeImages"
  • "appstream:DescribeUserStackAssociations"
  • "appstream:DescribeUsers"
  • "appstream:DescribeSessions"
  • "appstream:DescribeApplicationFleetAssociations"
  • "appstream:DescribeApplications"
  • "appstream:ListTagsForResource"

Polling frequency

Site24x7 queries the CloudWatch and other AWS service-level APIs as per the set polling frequency (one minute to a day) to collect metrics from Amazon AppStream 2.0.

Viewing performance data

To view AWS Systems Manager performance data on the Site24x7 web client:

  1. Go to Cloud > AWS and click your monitored AWS account.
  2. Choose AppStream 2.0. From the list of monitored AppStream 2.0 entities, choose the one for which you want to view metrics.
  3. View all the graphed metrics in the Summary tab.

Performance metrics supported

Metrics name Description Statistics Unit
 Actual Capacity  The total number of instances that are available for streaming or are currently streaming  Maximum  Count
 Available Capacity  The number of idle instances currently available for user sessions  Minimum  Count
 Capacity Utilization  The percentage of instances in a fleet that are being used  Average  Percent
 Desired Capacity  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  Maximum  Count
 In Use Capacity  The number of instances currently being used for streaming sessions. One In Use Capacity count represents one streaming session  Maximum  Count
 Pending Capacity  The number of instances being provisioned by AppStream 2.0. This 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  Maximum  Count
 Running Capacity  The total number of instances currently running. This represents the number of concurrent streaming sessions that can be supported by the fleet in its current state  Maximum  Count
 Insufficient Capacity Error  The number of session requests rejected due to lack of capacity  Maximum  Count
 Active Session Count API  The number of active sessions with API authentication  -  Count
 Active Session Count SAML  The number of active sessions with SAML authentication  -  Count
 Active Session Count User pool  The number of active sessions with user pool authentication  -  Count
 Expired Session Count API  The number of expired sessions with API authentication  -  Count
 Expired Session Count SAML  The number of expired sessions with SAML authentication  -  Count
 Expired Session Count User Pool  The number of expired sessions with user pool authentication  -  Count
 Connected User API  The number of connected users with API authentication  -  Count
 Connected User SAML  The number of connected users with SAML authentication  -  Count
 Connected User Count User Pool  The number of connected users with user pool authentication  -  Count

Configure thresholds for your Amazon AppStream metrics so that you can receive notifications when thresholds are breached.

Amazon AppStream 2.0 data

Configuration

A fleet consists of streaming instances that run the image that you specify. The Configuration tab provides details on the fleet and its configuration.

  • Fleet Details: Obtain details like Name, Display Name, Region, Status, Created Time, Image Name, and Description.
  • Fleet Configuration: Obtain details like Instance Type, Fleet Type, Disconnect Timeout, Idle Disconnect Timeout, Maximum Session Duration, IAM Role ARN, Directory Name, and Organization Units (OUs).
  • Network Details: View details like Subnets, Subnet Groups, and Internet Enabled.

Image Details

This tab provides details about the image that the fleet uses. This includes Name, Display Name, State, Description, Platform, Image Builder Name, Allow Fleet, Visibility, Created Time, and Applications.

Stack Details

A stack consists of an associated fleet, user access policies, and storage configurations. This tab displays details about the stack that the fleet uses. A stack contains all user permission details.

  • Stack Configuration: View details like Name, Display Name, Feedback URL, Redirect URL, Embed Host, Created Time, and Endpoint List.
  • User Settings: Displays details like Clipboard (Copy from Local Device), Clipboard (aws.appstream.clipboard), File Upload, File Download, Printing to Local Device, Password Sign In for Local Directory, Smart Card Sign In for Local Directory, and Setting Group.
  • Storage Configuration: Shows details like Home Folders, Google Drive, and One Drive.

Streaming Sessions

This tab lists all the current streaming sessions to which the user is connected.

Applications

This tab lists all applications with the elastic fleet type.

Automation

You can add automations to start or stop an AppStream fleet. Go to Admin > IT Automation Templates (+) > Add Automation Templates. Once automations are added, you can schedule them to be executed one after the other.

Forecast

Estimate future values of the Capacity Utilization metric and make informed decisions about adding capacity or scaling your AWS infrastructure.

Licensing

Every Amazon AppStream 2.0 monitor is considered a basic monitor.

 

Was this document helpful?

Shortlink has been copied!