Troubleshoot AWS monitoring setup
Read below how you can troubleshoot issues regarding your Dynatrace deployment for AWS monitoring.
Make sure that you have the latest version of Environment ActiveGate. Earlier versions (ActiveGate version 1.159 and earlier) contained a property with a different name. Set that property instead:
ActiveGate versions 1.159 and earlier
[collector]
AWSAgentEnabled = true
You have two options:
-
Option 1.
Confirm that all ActiveGates that have AWS monitoring enabled can connect to AWS.
In case of role-based setup: Ensure that all ActiveGates that have AWS monitoring enabled have theActiveGate
role attached. -
Option 2.
Choose one ActiveGate you want to monitor your AWS account with. Any ActiveGate type will work as long as it can connect to AWS. On that ActiveGate edit thecustom.properties
file and set the following property totrue
:
Versions 1.159 and earlier
[collector]
AWSAgentEnabled = true
ActiveGate version 1.161 or later
[aws_monitoring]
aws_monitoring_enabled = true
On all the other ActiveGates, set the property to false
.
Add *.amazonaws.com
to your firewall's list of allowed domains.
An error might occur when attaching a role to an EC2 instance. In such cases, you can use curl
to retrieve the instance metadata to verify if the role is listed there. Use the following command:
curl http://169.254.169.254/latest/meta-data/iam/info
If the attached role is still not listed in the instance metadata, it often helps to reattach it.
For more information, see Instance Metadata and User Data.