Set up Dynatrace Managed for AWS monitoring
You can integrate Dynatrace with Amazon Web Services (AWS) for intelligent monitoring of services running in the Amazon Cloud. AWS integration helps you stay on top of the dynamics of your data center in the cloud.
Dynatrace can be deployed with or without Environment ActiveGate. While using the role-based access method, make sure that you meet one of the following deployment requirements:
For deployments with Environment ActiveGate, the Environment ActiveGate must be hosted in AWS.
For deployments without Environment ActiveGate, a Dynatrace Managed Server must be hosted in AWS.
Overview
Follow these basic steps to integrate Dynatrace Managed with Amazon Web Services (AWS):
All cloud services consume Davis data units (DDUs). The amount of DDU consumption per service instance depends on the number of monitored metrics and their dimensions (each metric dimension results in the ingestion of 1 data point; 1 data point consumes 0.001 DDUs).
AWS costs
Dynatrace makes Amazon API requests every five minutes. In addition to CloudWatch API calls, Dynatrace makes API calls to the monitored AWS services to learn about their instances, tags, etc. The list of called services and actions is available below in the Create the monitoring policy section.
Here's a rough estimate of AWS monitoring costs:
AWS service | Number of metrics | Daily cost per instance (USD) |
---|---|---|
Elastic Compute Cloud (EC2) | 7 | $0.02016 |
Elastic Block Store (EBS) | 8 | $0.02304 |
Elastic Load Balancer (ELB) | 11 | $0.03168 |
Relational Database Service (RDS) | 11 | $0.03168 |
DynamoDB | 15 | $0.06912 |
Lambda | 4 | $0.01152 |
Amazon will charge about $0.01 per 1,000 metrics requested from the CloudWatch API and include the cost in the bill for the AWS account you use with Dynatrace.
AWS monitoring policy
The AWS monitoring policy defines the minimal scope of permissions you need to give to Dynatrace to monitor the services running in your AWS account. Create it once and use it any time when enabling Dynatrace access to your AWS account. If you don't want to add permissions to all services, and just select permissions for certain services, consult the table below. The table contains a set of permissions that are required for all services (All monitored Amazon services) and, for each cloud service, a list of optional permissions specific to that service.
Name | Additional permissions |
---|---|
AWS Certificate Manager Private Certificate Authority | "acm-pca:ListCertificateAuthorities" |
All monitored Amazon services | "cloudwatch:GetMetricData", "cloudwatch:GetMetricStatistics", "cloudwatch:ListMetrics", "sts:GetCallerIdentity", "tag:GetResources", "tag:GetTagKeys", "ec2:DescribeAvailabilityZones" |
Amazon MQ | |
Amazon API Gateway | "apigateway:GET" |
AWS App Runner | "apprunner:ListServices" |
Amazon AppStream | "appstream:DescribeFleets" |
AWS AppSync | "appsync:ListGraphqlApis" |
Amazon Athena | "athena:ListWorkGroups" |
Amazon Aurora | "rds:DescribeDBClusters" |
Amazon EC2 Auto Scaling | "autoscaling:DescribeAutoScalingGroups" |
Amazon EC2 Auto Scaling (built-in) | "autoscaling:DescribeAutoScalingGroups" |
AWS Billing | |
Amazon Keyspaces | |
AWS Chatbot | |
Amazon CloudFront | "cloudfront:ListDistributions" |
AWS CloudHSM | "cloudhsm:DescribeClusters" |
Amazon CloudSearch | "cloudsearch:DescribeDomains" |
AWS CodeBuild | "codebuild:ListProjects" |
Amazon Cognito | |
Amazon Connect | |
Amazon Elastic Kubernetes Service (EKS) | "eks:ListClusters" |
AWS DataSync | "datasync:ListTasks" |
Amazon DynamoDB Accelerator (DAX) | "dax:DescribeClusters" |
Amazon Database Migration Service | "dms:DescribeReplicationInstances" |
Amazon DocumentDB | "rds:DescribeDBClusters" |
AWS Direct Connect | "directconnect:DescribeConnections" |
Amazon DynamoDB | "dynamodb:ListTables" |
Amazon DynamoDB (built-in) | "dynamodb:ListTables", "dynamodb:ListTagsOfResource" |
Amazon EBS | "ec2:DescribeVolumes" |
Amazon EBS (built-in) | "ec2:DescribeVolumes" |
Amazon EC2 API | |
Amazon EC2 (built-in) | "ec2:DescribeInstances" |
Amazon EC2 Spot Fleet | "ec2:DescribeSpotFleetRequests" |
Amazon Elastic Container Service (ECS) | "ecs:ListClusters" |
Amazon ECS ContainerInsights | "ecs:ListClusters" |
Amazon ElastiCache (EC) | "elasticache:DescribeCacheClusters" |
AWS Elastic Beanstalk | "elasticbeanstalk:DescribeEnvironments" |
Amazon Elastic File System (EFS) | "elasticfilesystem:DescribeFileSystems" |
Amazon Elastic Inference | |
Amazon Elastic Map Reduce (EMR) | "elasticmapreduce:ListClusters" |
Amazon Elasticsearch Service (ES) | "es:ListDomainNames" |
Amazon Elastic Transcoder | "elastictranscoder:ListPipelines" |
AWS Elastic Load Balancing (ELB) (built-in) | "elasticloadbalancing:DescribeInstanceHealth", "elasticloadbalancing:DescribeListeners", "elasticloadbalancing:DescribeLoadBalancers", "elasticloadbalancing:DescribeRules", "elasticloadbalancing:DescribeTags", "elasticloadbalancing:DescribeTargetHealth" |
Amazon EventBridge | "events:ListEventBuses" |
Amazon FSx | "fsx:DescribeFileSystems" |
Amazon GameLift | "gamelift:ListFleets" |
AWS Glue | "glue:GetJobs" |
Amazon Inspector | "inspector:ListAssessmentTemplates" |
AWS Internet of Things (IoT) | |
AWS IoT Analytics | |
Amazon Managed Streaming for Kafka | "kafka:ListClusters" |
Amazon Kinesis Data Analytics | "kinesisanalytics:ListApplications" |
Amazon Kinesis Data Firehose | "firehose:ListDeliveryStreams" |
Amazon Kinesis Data Streams | "kinesis:ListStreams" |
Amazon Kinesis Video Streams | "kinesisvideo:ListStreams" |
Amazon Lambda | "lambda:ListFunctions" |
AWS Lambda (built-in) | "lambda:ListFunctions", "lambda:ListTags" |
Amazon Lex | "lex:GetBots" |
AWS Application and Network Load Balancer (built-in) | "elasticloadbalancing:DescribeInstanceHealth", "elasticloadbalancing:DescribeListeners", "elasticloadbalancing:DescribeLoadBalancers", "elasticloadbalancing:DescribeRules", "elasticloadbalancing:DescribeTags", "elasticloadbalancing:DescribeTargetHealth" |
Amazon CloudWatch Logs | "logs:DescribeLogGroups" |
AWS Elemental MediaConnect | "mediaconnect:ListFlows" |
Amazon MediaConvert | "mediaconvert:DescribeEndpoints" |
Amazon MediaPackage Live | "mediapackage:ListChannels" |
Amazon MediaPackage Video on Demand | "mediapackage-vod:ListPackagingConfigurations" |
Amazon MediaTailor | "mediatailor:ListPlaybackConfigurations" |
Amazon VPC NAT Gateways | "ec2:DescribeNatGateways" |
Amazon Neptune | "rds:DescribeDBClusters" |
AWS OpsWorks | "opsworks:DescribeStacks" |
Amazon Polly | |
Amazon QLDB | "qldb:ListLedgers" |
Amazon RDS | "rds:DescribeDBInstances" |
Amazon RDS (built-in) | "rds:DescribeDBInstances", "rds:DescribeEvents", "rds:ListTagsForResource" |
Amazon Redshift | "redshift:DescribeClusters" |
Amazon Rekognition | |
AWS RoboMaker | "robomaker:ListSimulationJobs" |
Amazon Route 53 | "route53:ListHostedZones" |
Amazon Route 53 Resolver | "route53resolver:ListResolverEndpoints" |
Amazon S3 | "s3:ListAllMyBuckets" |
Amazon S3 (built-in) | "s3:ListAllMyBuckets" |
Amazon SageMaker Batch Transform Jobs | |
Amazon SageMaker Endpoint Instances | "sagemaker:ListEndpoints" |
Amazon SageMaker Endpoints | "sagemaker:ListEndpoints" |
Amazon SageMaker Ground Truth | |
Amazon SageMaker Processing Jobs | |
Amazon SageMaker Training Jobs | |
AWS Service Catalog | |
Amazon Simple Email Service (SES) | |
Amazon Simple Notification Service (SNS) | "sns:ListTopics" |
Amazon Simple Queue Service (SQS) | "sqs:ListQueues" |
AWS Systems Manager - Run Command | |
AWS Step Functions | |
AWS Storage Gateway | "storagegateway:ListGateways" |
Amazon SWF | "swf:ListDomains" |
Amazon Textract | |
AWS IoT Things Graph | |
Amazon Transfer Family | "transfer:ListServers" |
AWS Transit Gateway | "ec2:DescribeTransitGateways" |
Amazon Translate | |
AWS Trusted Advisor | |
AWS API Usage | |
AWS Site-to-Site VPN | "ec2:DescribeVpnConnections" |
Amazon WAF Classic | |
Amazon WAF | |
Amazon WorkMail | "workmail:ListOrganizations" |
Amazon WorkSpaces | "workspaces:DescribeWorkspaces" |
Access method
To get the information required for comprehensive AWS cloud-computing monitoring, Dynatrace needs to identify all the virtualized infrastructure components in your AWS environment and collect performance metrics related to those components. We use this information to understand the context of your applications, services, and hosts. For this to happen, you need to authorize Dynatrace to access your Amazon metrics.
Make sure that your Environment ActiveGate or Managed Cluster has a working connection to AWS. Configure your proxy for Managed or ActiveGate, or allow access to *.amazonaws.com
in your firewall settings.
Role-based access with Environment ActiveGate or Dynatrace Managed Server
The instructions below apply whether or not the account hosting your ActiveGate is the same as your monitored account.
In a typical setup, you need to create two CloudFormation stacks using CloudFormation templates:
- A CloudFormation stack from the account hosting your ActiveGate, containing the following resources:
A role for your Environment ActiveGate or Dynatrace Managed Server hosted in your AWS infrastructure, on an Amazon EC2 host.
Its attached policy, which defines the monitored account permissions.
- A CloudFormation stack from the monitored account, containing the following resources:
A dedicated monitoring role for Dynatrace in your AWS account.
Its attached policy, which defines the Dynatrace authentication permissions to your AWS environment.
Prerequisites for role-based access, with Environment ActiveGate or Dynatrace Managed Server
-
Dynatrace Managed Server installed on an Amazon EC2 host. It must be able to assume a role within your AWS account that allows it to read the Dynatrace monitoring data.
-
The ID of the AWS account that hosts the ActiveGate (for example, the account that hosts your Dynatrace components, which in this case is the one hosting Environment ActiveGate or Dynatrace Managed Server).
-
The Amazon Web Services monitored account ID (the account you want to monitor).
-
The name of the role with which your Environment ActiveGate or Dynatrace Managed Server was started.
-
The External ID.
- In the Dynatrace menu, go to Settings.
- Go to Cloud and virtualization > AWS and select Connect new instance.
- Under Authentication method, select Role-based authentication.
- Under Your Amazon account ID, select Copy to copy the token (the External ID).
To enable access to your Amazon account using role-based access, follow the steps below.
Create a role for ActiveGate on the account that hosts ActiveGate
Create a monitoring role for Dynatrace on your monitored account
Modify ActiveGate configuration
Create a role for ActiveGate on the account that hosts ActiveGate
- Create a YAML file and paste the contents of github
role_based_access_AG_account_template.yml
.
For each account you want to monitor, in the Resource section of the template above, add a new item to the !Sub
array in the following format: 'arn:aws:iam::<new_monitored_account_id>:role/<new_monitoring_role_name>'
.
Be sure to replace the placeholders (<new_monitored_account_id>
and <new_monitoring_role_name>
) with your own values.
Create the stack in your Amazon Console or using the CLI.
In your Amazon Console, go to CloudFormation.
- Go to Stacks and create a new stack with new resources.
- Select Template is ready, upload the template you created above, and select Next.
- In Parameters, for MonitoredAccountID, enter the ID of the account Dynatrace will monitor. Optionally, adapt other parameters as needed.
- Enter a name for your stack, and then select Next twice.
- Review your configuration, select I acknowledge that AWS CloudFormation might create IAM resources with custom names, and select Create stack.
Run the command below, making sure to replace the parameter values with your actual values.
You need to remove the angle brackets (<
and >
).
1aws cloudformation create-stack \2--capabilities CAPABILITY_NAMED_IAM \3--stack-name <stack_name> \4--template-body <file:///home/user/template_file.yaml> \5--parameters ParameterKey=ActiveGateRoleName,ParameterValue=<role_name> ParameterKey=AssumePolicyName,ParameterValue=<policy_name> ParameterKey=MonitoringRoleName,ParameterValue=<monitoring_role_name> ParameterKey=MonitoredAccountID,ParameterValue=<monitored_account_id>
-
Go to the Amazon EC2 console, right-click an instance hosting your Environment ActiveGate, and select Security > Modify IAM role.
-
Select the role you created at step 1 (for example, Dynatrace_ActiveGate_role), and select Apply.
Create a monitoring role for Dynatrace on your monitored account
After the Dynatrace_ActiveGate_role
is created on the account hosting the ActiveGate, create a role for the account to be monitored.
-
Create a YAML file and paste the content from the github
role_based_access_monitored_account_template.yml
. -
Create the stack in your Amazon Console or using the CLI.
-
In your Amazon Console, go to CloudFormation.
-
Go to Stacks and create a new stack with new resources.
-
Select Template is ready, upload the template you created above, and select Next.
-
In Parameters, enter:
- The External ID. For details, see Prerequisites
- The ActiveGateRoleName and the ActiveGateAccountID from the stack created in Step 1.
Optionally, adapt other parameters as needed.
- Enter a name for your stack, and then select Next twice.
- Review your configuration, enable I acknowledge that AWS CloudFormation might create IAM resources with custom names, and select Create stack.
Run the command below, making sure to replace the parameter values with your actual values.
You need to remove the angle brackets (
<
and>
).1aws cloudformation create-stack \2--capabilities CAPABILITY_NAMED_IAM \3--stack-name <stack_name> \4--template-body <file:///home/user/template_file.yaml> \5--parameters ParameterKey=ExternalID,ParameterValue=<external_id> ParameterKey=ActiveGateRoleName,ParameterValue=<activegate_role_name> ParameterKey=ActiveGateAccountID,ParameterValue=<activegate_account_id>6ParameterKey=RoleName,ParameterValue=<role_name> ParameterKey=PolicyName,ParameterValue=<policy_name> -
Modify ActiveGate configuration
Starting with ActiveGate version 1.217, AWS monitoring is enabled by default. For configuration details, see Customize ActiveGate properties. The following configuration settings refer to earlier ActiveGate versions.
-
Edit the
custom.properties
configuration file of the ActiveGate that you want to use for AWS monitoring. -
Set the following properties as below:
1[aws_monitoring]2use_aws_proxy_role = false3aws_monitoring_enabled = trueActiveGate version 1.183 or earlier
1[vertical.topology]2use_aws_proxy_role = false1[aws_monitoring]2aws_monitoring_enabled = trueMultiple ActiveGatesIt's enough to use only one ActiveGate dedicated for AWS monitoring. However, some deployment scenarios (for example, for redundancy purposes) might require multiple ActiveGates in your deployment.
Make sure that only properly configured ActiveGates have
aws_monitoring_enabled
set totrue
.They need network access to AWS endpoints.
For role-based monitoring, they must have proper roles attached.
Keep in mind that Dynatrace cluster nodes contain embedded ActiveGates. Make sure to set the
aws_monitoring_enabled
property tofalse
on these ActiveGates if they're not configured fully for AWS monitoring.If the ActiveGate is dedicated to AWS monitoring, you must also set the
MSGrouter
property tofalse
:1[collector]2MSGrouter = falseRemove
aws_proxy_account
andaws_proxy_role
properties. -
Save the file and restart the ActiveGate main service.
Key-based authentication is only allowed for AWS GovCloud and China partitions.
In this scenario, you have to create an AWS monitoring policy and generate a key pair with that policy.
AWS IAM permissions boundaries may prohibit AWS actions required by Dynatrace. If you use an IAM permissions boundary on your AWS account, make sure that the actions from that policy are allowed in all AWS regions within that permissions boundary.
To create the AWS monitoring policy
- In your Amazon Console, go to Identity and Access Management.
- Go to Policies and select Create policy.
- Select the JSON tab and paste the predefined policy from the box below.
1{2 "Version": "2012-10-17",3 "Statement": [4 {5 "Sid": "VisualEditor0",6 "Effect": "Allow",7 "Action": [8 "acm-pca:ListCertificateAuthorities",9 "apigateway:GET",10 "apprunner:ListServices",11 "appstream:DescribeFleets",12 "appsync:ListGraphqlApis",13 "athena:ListWorkGroups",14 "autoscaling:DescribeAutoScalingGroups",15 "cloudformation:ListStackResources",16 "cloudfront:ListDistributions",17 "cloudhsm:DescribeClusters",18 "cloudsearch:DescribeDomains",19 "cloudwatch:GetMetricData",20 "cloudwatch:GetMetricStatistics",21 "cloudwatch:ListMetrics",22 "codebuild:ListProjects",23 "datasync:ListTasks",24 "dax:DescribeClusters",25 "directconnect:DescribeConnections",26 "dms:DescribeReplicationInstances",27 "dynamodb:ListTables",28 "dynamodb:ListTagsOfResource",29 "ec2:DescribeAvailabilityZones",30 "ec2:DescribeInstances",31 "ec2:DescribeNatGateways",32 "ec2:DescribeSpotFleetRequests",33 "ec2:DescribeTransitGateways",34 "ec2:DescribeVolumes",35 "ec2:DescribeVpnConnections",36 "ecs:ListClusters",37 "eks:ListClusters",38 "elasticache:DescribeCacheClusters",39 "elasticbeanstalk:DescribeEnvironmentResources",40 "elasticbeanstalk:DescribeEnvironments",41 "elasticfilesystem:DescribeFileSystems",42 "elasticloadbalancing:DescribeInstanceHealth",43 "elasticloadbalancing:DescribeListeners",44 "elasticloadbalancing:DescribeLoadBalancers",45 "elasticloadbalancing:DescribeRules",46 "elasticloadbalancing:DescribeTags",47 "elasticloadbalancing:DescribeTargetHealth",48 "elasticmapreduce:ListClusters",49 "elastictranscoder:ListPipelines",50 "es:ListDomainNames",51 "events:ListEventBuses",52 "firehose:ListDeliveryStreams",53 "fsx:DescribeFileSystems",54 "gamelift:ListFleets",55 "glue:GetJobs",56 "inspector:ListAssessmentTemplates",57 "kafka:ListClusters",58 "kinesis:ListStreams",59 "kinesisanalytics:ListApplications",60 "kinesisvideo:ListStreams",61 "lambda:ListFunctions",62 "lambda:ListTags",63 "lex:GetBots",64 "logs:DescribeLogGroups",65 "mediaconnect:ListFlows",66 "mediaconvert:DescribeEndpoints",67 "mediapackage-vod:ListPackagingConfigurations",68 "mediapackage:ListChannels",69 "mediatailor:ListPlaybackConfigurations",70 "opsworks:DescribeStacks",71 "qldb:ListLedgers",72 "rds:DescribeDBClusters",73 "rds:DescribeDBInstances",74 "rds:DescribeEvents",75 "rds:ListTagsForResource",76 "redshift:DescribeClusters",77 "robomaker:ListSimulationJobs",78 "route53:ListHostedZones",79 "route53resolver:ListResolverEndpoints",80 "s3:ListAllMyBuckets",81 "sagemaker:ListEndpoints",82 "sns:ListTopics",83 "sqs:ListQueues",84 "storagegateway:ListGateways",85 "sts:GetCallerIdentity",86 "swf:ListDomains",87 "tag:GetResources",88 "tag:GetTagKeys",89 "transfer:ListServers",90 "workmail:ListOrganizations",91 "workspaces:DescribeWorkspaces"92 ],93 "Resource": "*"94 }95 ]96}
Give the policy a name.
- Select Create policy.
Dynatrace can use access keys to make secure REST or Query protocol requests to the AWS service API. You'll need to generate an Access key ID and a Secret access key that Dynatrace can use to get metrics from Amazon Web Services.
- In your Amazon Console, go to Users and select Add Users.
- Enter the User name.
- In the next screen, choose Attach policies directly and attach the policy that you created before.
- Review the user details and select Create user.
- From the list of users, select your newly created user name and go to Security credentials, then select Create access key.
- In the Access key best practices & alternatives screen, select Third-party service, then select Next.
- You will be transferred to the Retrieve access keys screen, where both your Access key and a Secret access key are present.
- Store the Access Key ID name (AKID) and Secret access key values.
- You can either download the user credentials or copy the credentials displayed online (select Show).
Connect your Amazon account
Once you've granted AWS access to Dynatrace, it's time to connect Dynatrace to your Amazon AWS account.
-
In Dynatrace, go to Settings > Cloud and virtualization > AWS and select Connect new instance.
-
Select the Role-based authentication method.
- Create a name for this connection. If you leave this field empty, the name Role will be used on Dynatrace pages to define this connection.
- In the Role field, type the name of the role you created in Amazon for Dynatrace (for example,
Dynatrace_monitoring_role
). - Type your Account ID (the account you want us to pull metrics from).
- Select Connect to verify and save the connection.
-
Once the connection is successfully verified and saved, your AWS account will be listed in the Cloud and virtualization settings page.
You should soon begin to see AWS cloud monitoring data.
Select your AWS partition
If your AWS account is on a different partition than the default aws
partition, you can select it and Dynatrace will connect to it instead.
To change your AWS partition
- In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS.
- Find the instance where you want to change the partition and select
to edit the instance.
- In the AWS partition list, select your partition.
- Select Save.
Adjust monitoring to your needs
You can alter the scope and content of your monitoring depending on your preferences by using tags and listing services needed.
Limit monitored resources using tags
We recommend that you limit the scope of your AWS monitoring and reduce the number API calls to Amazon. You can use tagging to limit the AWS resources (AWS service instances) that are monitored by Dynatrace.
Set up metric events for alerting
To configure metric events for alerting
- In the Dynatrace menu, go to Settings > Cloud and virtualization > AWS.
- Under Metric events for alerting, select Manage alerting rules.
- On the Metric events for alerting page, you can create, enable/disable, and configure recommended alerting rules.
For an overview of all recommended alerting rules for all supporting services, see the list below.
Name | Alerting rules |
---|---|
Amazon MQ | Amazon MQ store percent usage (Static threshold: above 95 %), Amazon MQ temp percent usage (Static threshold: above 95 %), Amazon MQ memory usage (by topic) (Static threshold: above 95 %), Amazon MQ memory usage (by queue) (Static threshold: above 95 %), Amazon MQ CPU utilization (Static threshold: above 95 %), Amazon MQ heap usage (Static threshold: above 95 %), Amazon MQ job scheduler store percent usage (Static threshold: above 95 %), Amazon RabbitMQ CPU utilization (Static threshold: above 95 %) |
AWS App Runner | AWS App Runner CPU utilization (by instance/service ID) (Static threshold: above 95 %) |
Amazon AppStream | Amazon AppStream capacity utilization (Static threshold: above 95 %) |
Amazon Aurora | Amazon Aurora CPU utilization (average, by region) (Static threshold: above 95 %), Amazon Aurora CPU utilization (average, by region/engine) (Static threshold: above 95 %), Amazon Aurora CPU utilization (average, by region/database class) (Static threshold: above 95 %), Amazon Aurora CPU utilization (average) (Static threshold: above 95 %), Amazon Aurora CPU utilization (average, by role) (Static threshold: above 95 %), Amazon Aurora CPU utilization (maximum, by region) (Static threshold: above 95 %), Amazon Aurora CPU utilization (maximum, by region/engine) (Static threshold: above 95 %), Amazon Aurora CPU utilization (maximum, by region/database class) (Static threshold: above 95 %), Amazon Aurora CPU utilization (maximum) (Static threshold: above 95 %), Amazon Aurora CPU utilization (maximum, by role) (Static threshold: above 95 %) |
Amazon Keyspaces | Amazon Keyspaces account provisioned read capacity utilization (by region) (Static threshold: above 95 %), Amazon Keyspaces account provisioned write capacity utilization (by region) (Static threshold: above 95 %), Amazon Keyspaces max provisioned table read capacity utilization (by region) (Static threshold: above 95 %), Amazon Keyspaces max provisioned table write capacity utilization (by region) (Static threshold: above 95 %) |
Amazon CloudFront | Amazon CloudFront total error rate (by region) (Static threshold: above 5 %), Amazon CloudFront 4xx error rate (by region) (Static threshold: above 5 %), Amazon CloudFront 5xx error rate (by region) (Static threshold: above 5 %) |
Amazon CloudSearch | Amazon CloudSearch index utilization (Static threshold: above 95 %) |
AWS CodeBuild | AWS CodeBuild CPU utilized percent (Static threshold: above 95 %), AWS CodeBuild CPU utilized percent (by build id/build number) (Static threshold: above 95 %), AWS CodeBuild memory utilized percent (Static threshold: above 95 %), AWS CodeBuild memory utilized percent (by build id/build number) (Static threshold: above 95 %) |
Amazon Connect | Amazon Connect the percentage of the concurrent calls service quota (by metric group) (Static threshold: above 95 %) |
Amazon Elastic Kubernetes Service (EKS) | Amazon EKS Node CPU utilization (by instance id/node name) (Static threshold: above 95 %), Amazon EKS Node memory utilization (by instance id/node name) (Static threshold: above 95 %), Amazon EKS Pod CPU utilization over pod limit (by namespace) (Static threshold: above 95 %), Amazon EKS Pod CPU utilization over pod limit (by namespace/pod name) (Static threshold: above 95 %), Amazon EKS Pod CPU utilization over pod limit (Static threshold: above 95 %), Amazon EKS Node filesystem utilization (by instance id/node name) (Static threshold: above 95 %), Amazon EKS Pod memory utilization (by namespace) (Static threshold: above 95 %), Amazon EKS Pod memory utilization (by namespace/pod name) (Static threshold: above 95 %), Amazon EKS Service Pod memory utilization (Static threshold: above 95 %), Amazon EKS Pod CPU utilization (by namespace) (Static threshold: above 95 %), Amazon EKS Pod CPU utilization (by namespace/pod name) (Static threshold: above 95 %), Amazon EKS Pod CPU utilization (Static threshold: above 95 %), Amazon EKS Pod CPU reserved capacity (by namespace/pod name) (Static threshold: above 95 %), Amazon EKS Pod CPU reserved capacity (Static threshold: above 95 %), Amazon EKS Pod memory utilization over pod limit (by namespace) (Static threshold: above 95 %), Amazon EKS Pod memory utilization over pod limit (by namespace/pod name) (Static threshold: above 95 %), Amazon EKS Pod memory utilization over pod limit (Static threshold: above 95 %), Amazon EKS Pod memory reserved capacity (by namespace/pod name) (Static threshold: above 95 %), Amazon EKS Pod memory reserved capacity (Static threshold: above 95 %), Amazon EKS Node CPU reserved capacity (by instance id/node name) (Static threshold: above 95 %), Amazon EKS Node CPU reserved capacity (Static threshold: above 95 %), Amazon EKS Node memory reserved capacity (by instance id/node name) (Static threshold: above 95 %), Amazon EKS Node memory reserved capacity (Static threshold: above 95 %), Amazon EKS Node CPU utilization (Static threshold: above 95 %), Amazon EKS Node memory utilization (Static threshold: above 95 %), Amazon EKS Node filesystem utilization (Static threshold: above 95 %) |
Amazon DynamoDB Accelerator (DAX) | Amazon DynamoDB Accelerator CPU utilization (Static threshold: above 95 %), Amazon DynamoDB Accelerator CPU utilization (by node id) (Static threshold: above 95 %), Amazon DynamoDB Accelerator CPU utilization (by region) (Static threshold: above 95 %) |
Amazon Database Migration Service | Amazon Database Migration Service CPU utilization (by replication task identifier) (Static threshold: above 95 %), Amazon Database Migration Service CPU utilization (Static threshold: above 95 %), Amazon Database Migration Service CPU utilization (by replication instance/external resource id) (Static threshold: above 95 %), Amazon Database Migration Service CPU utilization (by region) (Static threshold: above 95 %), Amazon Database Migration Service CPU utilization (by region/instance class) (Static threshold: above 95 %) |
Amazon DocumentDB | Amazon DocumentDB CPU utilization (by region/DB instance identifier) (Static threshold: above 95 %), Amazon DocumentDB CPU utilization (by role) (Static threshold: above 95 %), Amazon DocumentDB CPU utilization (Static threshold: above 95 %) |
Amazon Elastic Container Service (ECS) | Amazon ECS CPU reservation (Static threshold: above 95 %), Amazon ECS CPU utilization (Static threshold: above 95 %), Amazon ECS CPU utilization (by service name) (Static threshold: above 95 %), Amazon ECS Memory reservation (Static threshold: above 95 %), Amazon ECS Memory utilization (Static threshold: above 95 %), Amazon ECS Memory utilization (by service name) (Static threshold: above 95 %) |
Amazon ECS ContainerInsights | Amazon ECS ContainerInsights instance memory utilization (by container instance id/instance id) (Static threshold: above 95 %), Amazon ECS ContainerInsights instance memory utilization (Static threshold: above 95 %), Amazon ECS ContainerInsights instance memory reserved capacity (by container instance id/instance id) (Static threshold: above 95 %), Amazon ECS ContainerInsights instance memory reserved capacity (Static threshold: above 95 %), Amazon ECS ContainerInsights instance CPU utilization (by container instance id/instance id) (Static threshold: above 95 %), Amazon ECS ContainerInsights instance CPU utilization (Static threshold: above 95 %), Amazon ECS ContainerInsights instance filesystem utilization (by container instance id/instance id) (Static threshold: above 95 %), Amazon ECS ContainerInsights instance filesystem utilization (Static threshold: above 95 %), Amazon ECS ContainerInsights instance CPU reserved capacity (by container instance id/instance id) (Static threshold: above 95 %), Amazon ECS ContainerInsights instance CPU reserved capacity (Static threshold: above 95 %) |
Amazon ElastiCache (EC) | Amazon ElastiCache CPU utilization (Static threshold: above 95 %), Amazon ElastiCache CPU utilization (by cache/node id) (Static threshold: above 95 %), Amazon ElastiCache engine CPU utilization (Static threshold: above 95 %), Amazon ElastiCache engine CPU utilization (by cache/node id) (Static threshold: above 95 %) |
AWS Elastic Beanstalk | AWS Elastic Beanstalk root filesystem util (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk root filesystem util (Static threshold: above 95 %), AWS Elastic Beanstalk load average 1min (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk load average 5min (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk CPU user (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk CPU nice (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk CPU idle (by instance id) (Static threshold: below 5 %), AWS Elastic Beanstalk CPU IO wait (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk CPU irq (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk CPU softirq (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk CPU system (by instance id) (Static threshold: above 95 %), AWS Elastic Beanstalk CPU privileged (by instance id) (Static threshold: above 95 %) |
Amazon Elastic File System (EFS) | Amazon EFS percent IO limit (Static threshold: above 95 %) |
Amazon Elastic Inference | Amazon Elastic Inference accelerator utilization (by Elastic Inference accelerator id) (Static threshold: above 95 %) |
Amazon Elastic Map Reduce (EMR) | Amazon Elastic MapReduce YARN memory available percentage (Static threshold: below 5 %), Amazon Elastic MapReduce YARN memory available percentage (by job id) (Static threshold: below 5 %), Amazon Elastic MapReduce HDFS utilization (Static threshold: above 95 %), Amazon Elastic MapReduce HDFS utilization (by job id) (Static threshold: above 95 %) |
Amazon Elasticsearch Service (ES) | Amazon Elasticsearch Service CPU utilization (maximum, by client id) (Static threshold: above 95 %), Amazon Elasticsearch Service CPU utilization (by client id) (Static threshold: above 95 %), Amazon Elasticsearch Service JVM memory pressure (high, by client id) (Static threshold: above 75 %), Amazon Elasticsearch Service JVM memory pressure (critical, by client id) (Static threshold: above 90 %), Amazon Elasticsearch Service master CPU utilization (by client id) (Static threshold: above 95 %), Amazon Elasticsearch Service master JVM memory pressure (high) (Static threshold: above 75 %), Amazon Elasticsearch Service master JVM memory pressure (critical) (Static threshold: above 90 %) |
Amazon GameLift | Amazon GameLift percent idle instances (Static threshold: below 5 %), Amazon GameLift percent idle instances (by region/metric groups) (Static threshold: below 5 %), Amazon GameLift percent healthy server processes (Static threshold: below 95 %), Amazon GameLift Percent healthy server processes (by region/metric groups) (Static threshold: below 95 %), Amazon GameLift percent available game sessions (Static threshold: below 5 %), Amazon GameLift percent available game sessions (by region/metric groups) (Static threshold: below 5 %) |
AWS Glue | AWS Glue driver JVM heap usage (by job run id/type) (Static threshold: above 95 %), AWS Glue ALL JVM heap usage (by job run id/type) (Static threshold: above 95 %), AWS Glue driver CPU system load (by job run id/type) (Static threshold: above 95 %), AWS Glue ALL CPU system load (by job run id/type) (Static threshold: above 95 %) |
Amazon Managed Streaming for Kafka | Amazon Managed Streaming for Kafka root disk used (by broker id) (Static threshold: above 95 %), Amazon Managed Streaming for Kafka network processor avg idle percent (by broker id) (Static threshold: below 5 %), Amazon Managed Streaming for Kafka request handler avg idle percent (by broker id) (Static threshold: below 5 %), Amazon Managed Streaming for Kafka app logs disk used (by broker id) (Static threshold: above 95 %), Amazon Managed Streaming for Kafka data logs disk used (by broker id) (Static threshold: above 95 %), Amazon Managed Streaming for Kafka the percentage of CPU in user space (by broker id) (Static threshold: above 95 %), Amazon Managed Streaming for Kafka the percentage of CPU idle time (by broker id) (Static threshold: below 5 %), Amazon Managed Streaming for Kafka the percentage of CPU in kernel space (by broker id) (Static threshold: above 95 %) |
AWS Elemental MediaConnect | AWS Elemental MediaConnect source packet loss percent (Static threshold: above 5 %), AWS Elemental MediaConnect packet loss percent (by region) (Static threshold: above 5 %), AWS Elemental MediaConnect packet loss percent (by region/availability zone) (Static threshold: above 5 %), AWS Elemental MediaConnect source packet loss percent (by region) (Static threshold: above 5 %), AWS Elemental MediaConnect source packet loss percent (by region/availability zone) (Static threshold: above 5 %), AWS Elemental MediaConnect source packet loss percent (by region/source arn) (Static threshold: above 5 %), AWS Elemental MediaConnect packet loss percent (Static threshold: above 5 %) |
Amazon Neptune | Amazon Neptune CPU utilization (Static threshold: above 95 %), Amazon Neptune CPU utilization (by role) (Static threshold: above 95 %), Amazon Neptune CPU utilization (by region) (Static threshold: above 95 %), Amazon Neptune CPU utilization (by region/DB instance identifier) (Static threshold: above 95 %), Amazon Neptune CPU utilization (by region/database class) (Static threshold: above 95 %), Amazon Neptune CPU utilization (by region/engine name) (Static threshold: above 95 %) |
AWS OpsWorks | AWS OpsWorks CPU system (Static threshold: above 95 %), AWS OpsWorks CPU user (Static threshold: above 95 %), AWS OpsWorks CPU nice (Static threshold: above 95 %), AWS OpsWorks CPU IO wait (Static threshold: above 95 %), AWS OpsWorks CPU steal (Static threshold: above 95 %), AWS OpsWorks CPU idle (Static threshold: below 5 %), AWS OpsWorks CPU system (by region/instance id) (Static threshold: above 95 %), AWS OpsWorks CPU system (by region/layer id) (Static threshold: above 95 %), AWS OpsWorks CPU user (by region/instance id) (Static threshold: above 95 %), AWS OpsWorks CPU user (by region/layer id) (Static threshold: above 95 %), AWS OpsWorks CPU nice (by region/instance id) (Static threshold: above 95 %), AWS OpsWorks CPU nice (by region/layer id) (Static threshold: above 95 %), AWS OpsWorks CPU IO wait (by region/instance id) (Static threshold: above 95 %), AWS OpsWorks CPU IO wait (by region/layer id) (Static threshold: above 95 %), AWS OpsWorks CPU steal (by region/instance id) (Static threshold: above 95 %), AWS OpsWorks CPU steal (by region/layer id) (Static threshold: above 95 %), AWS OpsWorks CPU idle (by region/instance id) (Static threshold: below 5 %), AWS OpsWorks CPU idle (by region/layer id) (Static threshold: below 5 %) |
Amazon Redshift | Amazon Redshift CPU utilization (Static threshold: above 95 %), Amazon Redshift CPU utilization (by node id) (Static threshold: above 95 %), Amazon Redshift percentage disk space used (Static threshold: above 95 %), Amazon Redshift percentage disk space used (by node id) (Static threshold: above 95 %) |
Amazon Route 53 | Amazon Route 53 percentage healthy (by region/health check id) (Static threshold: below 95 %) |
Amazon SageMaker Batch Transform Jobs | Amazon SageMaker Batch Transform Jobs CPU utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Batch Transform Jobs memory utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Batch Transform Jobs GPU utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Batch Transform Jobs GPU memory utilization (by region/host) (Static threshold: above 95 %) |
Amazon SageMaker Endpoint Instances | Amazon SageMaker Endpoint Instances CPU utilization (by variant name) (Static threshold: above 95 %), Amazon SageMaker Endpoint Instances memory utilization (by variant name) (Static threshold: above 95 %), Amazon SageMaker Endpoint Instances GPU utilization (by variant name) (Static threshold: above 95 %), Amazon SageMaker Endpoint Instances GPU memory utilization (by variant name) (Static threshold: above 95 %), Amazon SageMaker Endpoint Instances disk utilization (by variant name) (Static threshold: above 95 %) |
Amazon SageMaker Processing Jobs | Amazon SageMaker Processing Jobs CPU utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Processing Jobs memory utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Processing Jobs GPU utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Processing Jobs GPU memory utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Processing Jobs disk utilization (by region/host) (Static threshold: above 95 %) |
Amazon SageMaker Training Jobs | Amazon SageMaker Training Jobs CPU utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Training Jobs memory utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Training Jobs GPU utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Training Jobs GPU memory utilization (by region/host) (Static threshold: above 95 %), Amazon SageMaker Training Jobs disk utilization (by region/host) (Static threshold: above 95 %) |
Amazon Simple Email Service (SES) | Amazon SES reputation bounce rate (by region) (Static threshold: above 5 %), Amazon SES reputation complaint rate (by region) (Static threshold: above 0.1 %) |
AWS Storage Gateway | AWS Storage Gateway cache percent dirty (by region/share id) (Static threshold: above 80 %), AWS Storage Gateway cache percent dirty (by region/volume id) (Static threshold: above 80 %), AWS Storage Gateway cache percent dirty (by gateway id) (Static threshold: above 80 %), AWS Storage Gateway user CPU percent (Static threshold: above 95 %), AWS Storage Gateway IO wait percent (Static threshold: above 20 %), AWS Storage Gateway upload buffer percent used (by gateway id) (Static threshold: above 95 %), AWS Storage Gateway working storage percent used (by gateway id) (Static threshold: above 95 %) |
AWS Trusted Advisor | AWS Trusted Advisor service limit usage (by region/service limit/service name) (Static threshold: above 95 %) |
The number of recommended alerting rules depends on the number of your monitored supporting services.
To add recommended alerting rules for a new supporting service, you first need to add the new service to monitoring.
- In the Dynatrace menu, go to Settings > Cloud and virtualization > AWS.
- On the AWS overview page, select the edit button (pencil icon) for the AWS instance you want to edit.
- Select Manage services and Add service, choose the service name from the list, and select Add service.
- Select Save changes.
Note that not all supporting services have their own predefined alerting rules.
-
Create and enable alerting rules.
To enable recommended alerting rules, you first need to create them. You can create alerting rules and automatically enable them, or (if you clear Automatically enable created rules) create them and manually enable them after possible configuration changes.
For example, you can create and automatically enable a first batch of alerts. When you start monitoring new services, you can create alerts for these new services without automatically enabling them (because you want to configure them first).
-
Configure alerting rules. How you edit rules depends on whether you chose to automatically enable alerts.
-
If you chose to automatically enable alerts when creating them, go to Adjust recommended alerting rules, expand Enabled recommended alerting rules, and select any rule. This takes you to Edit custom event for alerting, where you can change the configuration rules for that specific service.
-
If you didn't choose to automatically enable alerts when creating them, go to Enable recommended alerting rules, expand Disabled recommended alerting rules, and select any of the disabled rules. This takes you to the same Edit custom event for alerting page.
-
-
Disable alerting rules.
-
You can disable all alerting rules, or disable or delete them selectively.
- To disable all alerting rules, go to Adjust recommended alerting rules and select Disable all enabled recommended alerting rules.
- To disable or delete alerting rules selectively, go to Adjust recommended alerting rules and select Metric events. On the Metric events page, you can disable an alert by turning it off in the On/Off column, or you can delete it by selecting
x
in the Delete column.
If you disable any or all of the alerting rules, you can always re-enable them.
Choose Cloud services to be monitored
Once your credentials are saved, you can decide which services will be monitored. To select your preferred services
- In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS.
- Find the instance where you want to perform your monitoring and select
to edit the instance.
- In the Services section, select Manage services.
- The following services are added by default: Amazon EC2, Amazon Lambda, Amazon RDS, Amazon DynamoDB, Amazon ALB, Amazon ELB, Amazon S3, and Amazon EBS. You can extend this list by choosing services from the dropdown menu. The full list of services is also available at All AWS cloud services.
- Select Add service
- Select the service from the list and then select Add service.
- Select Save changes to save your configuration.