Amazon AppStream 2.0

Dynatrace ingests metrics for multiple preselected namespaces, including Amazon AppStream 2.0. You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.

Prerequisites

To enable monitoring for this service, you need

an Environment or Cluster ActiveGate version 1.197+
Dynatrace version 1.201+
An updated AWS monitoring policy to include the additional AWS services.
To update the AWS IAM policy, use the JSON below.

Predefined policy in JSON

Download

{
   "Version": "2012-10-17",
   "Statement": [
      {
         "Sid": "VisualEditor0",
         "Effect": "Allow",
         "Action": [
            "ec2:DescribeInstances",
            "support:DescribeTrustedAdvisorCheckResult",
            "athena:ListWorkGroups",
            "elasticbeanstalk:DescribeEnvironmentResources",
            "appsync:ListGraphqlApis",
            "kinesis:ListStreams",
            "elasticbeanstalk:DescribeEnvironments",
            "ec2:DescribeVolumes",
            "support:DescribeTrustedAdvisorCheckSummaries",
            "kinesisanalytics:ListApplications",
            "codebuild:ListProjects",
            "datasync:ListTasks",
            "mediaconnect:ListFlows",
            "cloudformation:ListStackResources",
            "mediatailor:ListPlaybackConfigurations",
            "support:SearchForCases",
            "lambda:ListFunctions",
            "support:DescribeCases",
            "chatbot:DescribeSlackChannels",
            "transfer:ListServers",
            "cloudwatch:GetMetricStatistics",
            "support:DescribeAttachment",
            "chatbot:DescribeSlackWorkspaces",
            "workmail:ListOrganizations",
            "firehose:ListDeliveryStreams",
            "eks:ListClusters",
            "ec2:DescribeSubnets",
            "swf:ListDomains",
            "support:DescribeTrustedAdvisorCheckRefreshStatuses",
            "tag:GetResources",
            "dynamodb:ListTables",
            "qldb:ListLedgers",
            "sns:ListTopics",
            "dynamodb:ListTagsOfResource",
            "dax:DescribeClusters",
            "support:DescribeTrustedAdvisorChecks",
            "cloudwatch:ListMetrics",
            "cloudhsm:DescribeClusters",
            "storagegateway:ListGateways",
            "ec2:DescribeAvailabilityZones",
            "lambda:ListTags",
            "rds:DescribeDBInstances",
            "support:DescribeSeverityLevels",
            "cloudsearch:DescribeDomains",
            "rds:DescribeEvents",
            "dms:DescribeReplicationInstances",
            "route53:ListHostedZones",
            "events:ListEventBuses",
            "chatbot:DescribeChimeWebhookConfigurations",
            "ec2:DescribeSecurityGroups",
            "es:ListDomainNames",
            "rds:ListTagsForResource",
            "s3:ListAllMyBuckets",
            "ec2:DescribeVpcs",
            "opsworks:DescribeStacks",
            "kinesisvideo:ListStreams",
            "chatbot:DescribeSlackChannelConfigurations",
            "chatbot:GetSlackOauthParameters",
            "elastictranscoder:ListPipelines",
            "elasticloadbalancing:DescribeLoadBalancers",
            "autoscaling:DescribeAutoScalingGroups",
            "support:DescribeSupportLevel",
            "support:DescribeCaseAttributes",
            "elasticloadbalancing:DescribeInstanceHealth",
            "apigateway:GET",
            "workspaces:DescribeWorkspaces",
            "support:DescribeServices",
            "support:DescribeCommunications",
            "support:DescribeIssueTypes",
            "elasticloadbalancing:DescribeRules",
            "elasticache:DescribeCacheClusters",
            "fsx:DescribeFileSystems",
            "kafka:ListClusters",
            "cloudwatch:GetMetricData",
            "route53resolver:ListResolverEndpoints",
            "tag:GetTagKeys",
            "ec2:DescribeNetworkInterfaces",
            "elasticloadbalancing:DescribeListeners",
            "elasticmapreduce:ListClusters",
            "appstream:DescribeFleets",
            "elasticfilesystem:DescribeFileSystems",
            "ecs:ListClusters",
            "sqs:ListQueues",
            "logs:DescribeLogGroups",
            "elasticloadbalancing:DescribeTags",
            "mediaconvert:DescribeEndpoints",
            "ec2:DescribeNatGateways",
            "robomaker:ListSimulationJobs",
            "ec2:DescribeSpotFleetRequests",
            "mediapackage:ListChannels",
            "cloudfront:ListDistributions",
            "elasticloadbalancing:DescribeTargetHealth",
            "redshift:DescribeClusters",
            "mediapackage-vod:ListPackagingGroups",
            "mediapackage-vod:ListPackagingConfigurations",
            "sts:GetCallerIdentity",
            "rds:DescribeDBClusters",
            "directconnect:DescribeConnections"
         ],
         "Resource": "*"
      }
   ]
}

Add the service to monitoring

In order to view the service metrics, you must add the service to monitoring in your Dynatrace environment.

To add a service to monitoring

Go to Settings > Cloud and virtualization and select AWS.
On the AWS overview page, scroll down and select the desired AWS instance. Select the Edit button.
Scroll down and select Add service. Choose the service name from the drop-down and select Add service.
Select Save changes.

Configure service metrics

Once you add a service, Dynatrace starts automatically collecting a suite of metrics for this particular service. These are recommended metrics.

Recommended metrics:

Are enabled by default
Can't be disabled
Can have recommended dimensions (enabled by default, can't be disabled)
Can have optional dimensions (disabled by default, can be enabled)

Apart from the recommended metrics, most services have the possibility of enabling optional metrics.

Optional metrics:

Can be added and configured manually

To add and configure metrics

Go to Settings > Cloud and virtualization and select AWS.
On the AWS overview page, scroll down and select the desired AWS instance. Select the Edit button.
Scroll down to the Supporting services section and select Manage services.
To add a metric, select the service for which you want to add metrics.
Select Add metric.
From the menu, select the metric you want.
Select Add metric to add the metric to monitoring.
To configure a metric, select the Edit button associated to it.
Select Apply to save your configuration.

Import preset dashboards

Dynatrace provides preset AWS dashboards that you can import from GitHub to your environment's dashboard page. Once you download a preset dashboard locally, there are two ways to import it.

Import via Dynatrace web UI

On your Dynatrace dashboard page, select Edit and switch to Settings.
Select Advanced settings.
On the Dashboard settings menu, select Dashboard JSON.
Use Upload to choose and upload the dashboard JSON file that you want to import.

Import via Dynatrace API

Create an API token.
When creating the token, enable the Write configuration permission.
To import the dashboard, run the command below, replacing {DYNATRACE_HOST}, {DYNATRACE_TENANT}, {TOKEN}, and {PATH_TO_DASHBOARD} with your own values.

curl --location --request POST 'http://{DYNATRACE_HOST}/e/{DYNATRACE_TENANT}/api/config/v1/dashboards' \
--header 'Authorization: Api-Token {TOKEN}' \
--header 'Content-Type: application/json' \
--data-binary '{PATH_TO_DASHBOARD}'

For more information, see Dashboards API - POST a dashboard

appstream

Available metrics

Name	Description	Unit	Statistics	Dimensions	Recommended
ActualCapacity	The total number of instances that are available for streaming or are currently streaming. `ActualCapacity` = `AvailableCapacity` + `InUseCapacity`.	Count	Multi	Fleet	✔️
AvailableCapacity	The number of idle instances currently available for user sessions. `AvailableCapacity` = `ActualCapacity` - `InUseCapacity`.	Count	Multi	Fleet	✔️
CapacityUtilization	The percentage of instances in a fleet that are being used, using the following formula. `CapacityUtilization` = (`InUseCapacity`/`ActualCapacity`) * 100.	Percent	Multi	Fleet	✔️
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`.	Count	Multi	Fleet	✔️
InUseCapacity	The number of instances currently being used for streaming sessions. One `InUseCapacity` count represents one streaming session.	Count	Multi	Fleet	✔️
InsufficientCapacityError	The number of session requests rejected due to lack of capacity.	Count	Sum	Fleet
PendingCapacity	The number of instances being provisioned by AppStream 2.0. 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.	Count	Multi	Fleet	✔️