AppDynamics Monitoring Extension for use with AWS Lambda

AWS Lambda Monitoring Extension

Use Case

AWS Lambda Monitoring Extension captures Lambda statistics from Amazon CloudWatch and displays them in the AppDynamics Metric Browser.
Note : By default, the Machine agent can only send a fixed number of metrics to the controller. This extension potentially reports thousands of metrics, so to change this limit, please follow the instructions mentioned here.


Please give the following permissions to the account being used to with the extension.


In order to use this extension, you do need a Standalone JAVA Machine Agent or SIM Agent. For more details on downloading these products, please visit here.

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.

Agent Compatibility:

Note : This extension is compatible with Machine Agent version 4.5.13 or later.

  1. If you are seeing warning messages while starting the Machine Agent, update the http-client and http-core JARs in {MACHINE_AGENT_HOME}/monitorsLibs to httpclient-4.5.9 and httpcore-4.4.12 to make this warning go away.
  2. To make this extension work on Machine Agent < 4.5.13:
    The http-client and http-core JARs in {MACHINE_AGENT_HOME}/monitorsLibs has to be manually be updated to httpclient-4.5.9 and httpcore-4.4.12.


  1. Run ‘mvn clean install’ from aws-lambda-monitoring-extension
  2. Copy and unzip AWSLambdaMonitor-<version>.zip from ‘target’ directory into <machine_agent_dir>/monitors/
  3. Edit config.yml file in AWSLambdaMonitor/conf and provide the required configuration (see Configuration section)
  4. Restart the Machine Agent.

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 the AppDynamics Metric Browser, look for Application Infrastructure Performance|<Tier>|Custom Metrics|AWS Lambda Monitor and you should be able to see all the metrics.


In order to use the extension, you need to update the config.yml file that is present in the extension folder. The following is an explanation of the configurable fields that are present in the config.yml file.
All Lambda metrics are available under the namespace AWS/Lambda and provide metrics for a single dimension, the “FunctionName”. When retrieving metrics, you must supply both the Value/s for the dimension.

  1. If SIM is enabled, then use the following metricPrefix metricPrefix: "Custom Metrics|AWS Lambda Monitor" else configure the “COMPONENT_ID” under which the metrics need to be reported.
    This can be done by changing the value of <COMPONENT_ID> in metricPrefix: "Server|Component:<COMPONENT_ID>|Custom Metrics|AWS Lambda Monitor|".
    For example,

    metricPrefix: "Server|Component:100|Custom Metrics|AWS Lambda Monitor|"
  2. Provide accessKey(required) and secretKey(required) of AWS account(s), also provide displayAccountName(any name that represents your account) and regions(required).

      - 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"]
  3. 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 “enableDecryption” of “credentialsDecryptionConfig” to true and provide the encryption key in “encryptionKey”
    For example,

    #Encryption key for Encrypted password.
        enableDecryption: "true"
        encryptionKey: "XXXXXXXX"
  4. Provide the dimension for the Lambda function you would like to monitor in that dimension.

    #Filters based on dimensions, values accepts comma separated values and regex patterns. If `.*` is used, all are monitored and if empty, none are monitored
      - name: "FunctionName"
        displayName: "function-name"
        values: ["eretail-demo", "corpsite-blog"]
  5. Configure the metrics section.

    For configuring the metrics, the following properties can be used:

    PropertyDefault valuePossible valuesDescription
    aliasmetric nameAny stringThe 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
    multiplier1Any numberValue with which the metric needs to be multiplied.
    convertnullAny key value mapSet of key value pairs that indicates the value to which the metrics need to be transformed. eg: UP:0, DOWN:1
    deltafalsetrue, falseIf enabled, gives the delta values of metrics instead of actual values.

    For example,

      - name: "Invocations"
        alias: "Invocations"
        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.

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.

Below is an example config for monitoring multiple accounts and regions:

  - 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"]

    enableDecryption: "false"


#Filters based on dimensions, values accepts comma separated values and regex patterns. If `.*` is used, all are monitored and if empty, none are monitored
  - name: "FunctionName"
    displayName: "function-name"
    values: ["eretail-demo", "corpsite-blog"]

#Allowed values are Basic and Detailed. Refer for more information
# Basic will fire CloudWatch API calls every 5 minutes
# Detailed will fire CloudWatch API calls every 1 minutes
cloudWatchMonitoring: "Basic"

      - metricName: "CurrItems"
        statType: "max"

      - metricName: "DecrHits"
        statType: "sum"

    excludeMetrics: ["DeleteMisses", "Get.*"]

      startTimeInMinsBeforeNow: 5
      endTimeInMinsBeforeNow: 0

    maxErrorRetrySize: 0

  noOfAccountThreads: 3
  noOfRegionThreadsPerAccount: 3
  noOfMetricThreadsPerRegion: 3

  us-east-1 :
  us-east-2 :
  us-west-1 :
  us-west-2 :
  ap-northeast-1 :
  ap-northeast-3 :
  ap-south-1 :
  ap-southeast-1 :
  ap-southeast-2 :
  ca-central-1 :
  cn-north-1 :
  cn-northwest-1 :
  eu-central-1 :
  eu-west-1 :
  eu-west-2 :
  eu-west-3 :
  sa-east-1 :
  us-gov-west-1 :

metricPrefix: "Server|Component:<TIER_ID>|Custom Metrics|AWS Lambda Monitor|"
#metricPrefix: "Custom Metrics|AWS Lambda Monitor|"


Typical metric path: Application Infrastructure Performance|<Tier>|Custom Metrics|Amazon Lambda|<Account Name>|<Region>|Function Name|<Function Name> followed by the metrics defined in the link below:

Credentials Encryption

Please visit this page to get detailed instructions on password encryption. The steps in this document will guide you through the whole process.

Extensions Workbench

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.

Support Tickets

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.

  1. Stop the running machine agent.
  2. Delete all existing logs under <MachineAgent>/logs.
  3. Please enable debug logging by editing the file <MachineAgent>/conf/logging/log4j.xml. Change the level value of the following <logger> elements to debug.
    <logger name=“com.singularity”>
    <logger name=“com.appdynamics”>
  4. Start the machine agent and please let it run for 10 mins. Then zip and upload all the logs in the directory <MachineAgent>/logs/*.
  5. Attach the zipped <MachineAgent>/conf/* directory here.
  6. Attach the zipped <MachineAgent>/monitors/ExtensionFolderYouAreHavingIssuesWith directory here.
    For any support related questions, you can also contact


Always feel free to fork and contribute any changes directly here on GitHub.


Extension Version2.0.6
Controller Compatibility4.5 or Later
Agent Compatibility4.5.13 or later
Last Update03/06/2021

List of changes to this extension can be found here

Release Notes

v2.0.5 and above - Updated to work with MachineAgent 21.x