Instrumenting AWS instances and Azure VMs

In Entuity, users will need to configure their Amazon Web Service (AWS) and Microsoft Azure instances to ensure that Entuity is able to monitor and collect information on them. It is essential that these are configured, because otherwise Entuity will not be able to collect all information for them.

Note, on Azure, if the allocated diagnostics space is exhausted, there is the potential for Entuity to stop gathering data. You should ensure that you have sufficient diagnostics space available to continue monitoring virtualization platforms. It is recommended that you periodically remove old WAD tables from the storage accounts to prevent running out of space and to avoid incurring unnecessary costs.

Important note: for both AWS and Azure, producing and storing diagnostic data incurs additional costs as does the retrieval of this data via Entuity. 

Please see the below articles for help on how to instrument:

• Azure VMs with any guest OSs
• AWS CloudWatch monitoring
  • Entuity v21.0 P02 upwards provides support for the AWS CloudWatch monitoring agent. The CloudWatch agent replaces the deprecated performance monitoring scripts (which are installed per instance), and caters for both Windows and Linux.
  • If you are using an earlier version of Entuity, please see the following articles for help in instrumenting AWS instances:
    • Archived - AWS Red Hat instances
    • Archived - AWS Amazon Linux instances
    • Archived - Windows AWS Instances instrumented using SSM