Captures Application ELB statistics from Amazon CloudWatch and displays them in the AppDynamics Metric Browser.
The extension needs to be able to connect to AWS CloudWatch in order to collect and send metrics.
To do this, you will have to either establish a remote connection in between the extension and the product,
or have an agent on the same machine running the product in order for the extension to collect and send the metrics.
mvn clean installfrom aws-elb-monitoring-extension directory
<MachineAgent_Dir>/monitors/AWSELBMonitorThe metricPrefix of the extension has to be configured as specified here. Please make sure that the right metricPrefix is chosen based on your machine agent deployment, otherwise this could lead to metrics not being visible in the controller.
Please place the extension in the "monitors" directory of your Machine Agent installation directory.
Do not place the extension in the "extensions" directory of your Machine Agent installation directory.
In order to use the extension, you need to update the config.yml file that is present in the extension folder.
The following is a step-by-step explanation of the configurable fields that are present in the
If SIM is enabled, then use the following metricPrefix -
metricPrefix: "Custom Metrics|AWS Application ELB|"
Else, configure the "COMPONENT_ID" under which the metrics need to be reported. This can be done by changing the value of
metricPrefix: "Server|Component:<COMPONENT_ID>|Custom Metrics|AWS Application ELB|".
metricPrefix: "Server|Component:100|Custom Metrics|AWS Application ELB|"
Provide accessKey(required) and secretKey(required) of your account(s), also provide displayAccountName(any name that represents your account) and
regions(required). If you are running this extension inside an EC2 instance which has IAM profile configured then you don’t have to configure accessKey and secretKey values, extension will use IAM profile to authenticate. You can provide multiple accounts and regions as below -
accounts: - awsAccessKey: "XXXXXXXX1" awsSecretKey: "XXXXXXXXXX1" displayAccountName: "TestAccount_1" regions: ["us-east-1","us-west-1","us-west-2"] - awsAccessKey: "XXXXXXXX2" awsSecretKey: "XXXXXXXXXX2" displayAccountName: "TestAccount_2" regions: ["eu-central-1","eu-west-1"]
If you want to encrypt the awsAccessKey and awsSecretKey then follow the “Credentials Encryption” section and provide the encrypted values in awsAccessKey and awsSecretKey. Configure
true and provide the encryption key in
#Encryption key for Encrypted password. credentialsDecryptionConfig: enableDecryption: "false" encryptionKey:
Provide all valid proxy information if you use it. If not, leave this section as is.
proxyConfig: host: port: username: password:
To report metrics from specific dimension values, configure the
Dimensions for AWS ELB are
For example to report metrics only from only
AvailabilityZone dimension with value
dimensions as below -
dimensions: - name: "AvailabilityZone" displayName: "AvailabilityZone" values: ["Sample"]
If you would like to monitor more than one dimension, you can do the following :
dimensions: - name: "LoadBalancer" displayName: "Load Balancer" values: ["Dev", "tools"] - name: "AvailabilityZone" displayName: "AvailabilityZone" values: ["Sample"]
If these fields are left empty, none of your instances will be monitored.
In order to monitor everything under a dimension, you can simply use “.*” to pull everything from your AWS Environment.
Configure the metrics section.
For configuring the metrics, the following properties can be used:
|Property||Default value||Possible values||Description|
|alias||metric name||Any string||The substitute name to be used in the metric browser instead of metric name.|
|statType||“ave”||“AVERAGE”, “SUM”, “MIN”, “MAX”||AWS configured values as returned by API|
|aggregationType||“AVERAGE”||“AVERAGE”, “SUM”, “OBSERVATION”||Aggregation qualifier|
|timeRollUpType||“AVERAGE”||“AVERAGE”, “SUM”, “CURRENT”||Time roll-up qualifier|
|clusterRollUpType||“INDIVIDUAL”||“INDIVIDUAL”, “COLLECTIVE”||Cluster roll-up qualifier|
|multiplier||1||Any number||Value with which the metric needs to be multiplied.|
|convert||null||Any key value map||Set of key value pairs that indicates the value to which the metrics need to be transformed. eg: UP:0, DOWN:1|
|delta||false||true, false||If enabled, gives the delta values of metrics instead of actual values.|
- name: "ConditionalCheckFailedRequests" alias: "ConditionalCheckFailedRequests" statType: "ave" delta: false multiplier: 1 aggregationType: "AVERAGE" timeRollUpType: "AVERAGE" clusterRollUpType: "INDIVIDUAL"
All these metric properties are optional, and the default value shown in the table is applied to the metric(if a property has not been specified) by default.
For several services AWS CloudWatch does not instantly update the metrics but it goes back in time to update that information.
This delay sometimes can take upto 5 minutes. The extension runs every minute(Detailed) or every 5 minutes (Basic) and gets the latest value at that time.
There may be a case where the extension may miss the value before CloudWatch updates it. In order to make sure we don’t do that,
the extension has the ability to look for metrics during a certain interval, where we already have set it to default at 5 minutes but you can
change it as per your requirements.
metricsTimeRange: startTimeInMinsBeforeNow: 10 endTimeInMinsBeforeNow: 5
This field is set as per the defaults suggested by AWS. You can change this if your limit is different.
The maximum number of retry attempts for failed requests that can be retried.
CloudWatch can be used in two formats, Basic and Detailed. You can specify how you would like to run the extension by specifying the chosen format here.
By default, the extension is set to Basic, which makes the extension run every 5 minutes.
Refer https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html for more information.
#Allowed values are Basic and Detailed. # Basic will fire CloudWatch API calls every 5 minutes # Detailed will fire CloudWatch API calls every 1 minutes cloudWatchMonitoring: "Basic"
Please avoid using tab (\t) when editing yaml files. Please copy all the contents of the config.yml file and go to Yaml Validator . On reaching the website, paste the contents and press the “Go” button on the bottom left.
If you get a valid output, that means your formatting is correct and you may move on to the next step.
Typical metric path: Application Infrastructure Performance|<Tier>|Custom Metrics|Amazon Application ELB|<Account Name>|<Region>|Table Name|<table name> followed by the metrics defined in the link below:
Please visit this page to get detailed instructions on accountAccessKey encryption. The steps in this document will guide you through the whole process.
Workbench is an inbuilt feature provided with each extension in order to assist you to fine tune the extension setup before you actually deploy it on the controller. Please review the following document on How to use the Extensions WorkBench
Please follow the steps listed in this troubleshooting-document in order to troubleshoot your issue. These are a set of common issues that customers might have faced during the installation of the extension. If these don’t solve your issue, please follow the last step on the troubleshooting-document to contact the support team.
If after going through the Troubleshooting Document you have not been able to get your extension working, please file a ticket and add the following information.
Please provide the following in order for us to assist you better.
Always feel free to fork and contribute any changes directly here on GitHub.
|Controller Compatibility||4.4 or Later|
|Last Update||22nd March, 2019|
List of changes to this extension can be found here