AWS API Gateway Monitoring Extension

Use Case

Captures statistics for APIs in the API Gateway from Amazon CloudWatch and displays them in the AppDynamics Metric Browser.

Prerequisites

1. Please give the following permissions to the account being used to with the extension.
   
   1. cloudwatch:ListMetrics
   2. cloudwatch:GetMetricStatistics
2. Before the extension is installed, the prerequisites mentioned here need to be met. Please do not proceed with the extension installation if the specified prerequisites are not met.
3. Download and install Apache Maven which is configured with Java 8 to build the extension artifact from source. You can check the java version used in maven using command mvn -v or mvn --version. If your maven is using some other java version then please download java 8 for your platform and set JAVA_HOME parameter before starting maven.
4. 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.

Installation

1. Clone the "aws-api-gateway-monitoring-extension" repo using git clone <repoUrl> command.
2. Run 'mvn clean install' from aws-api-gateway-monitoring-extension
3. Copy and unzip AWSAPIGatewayMonitor-<version>.zip from 'target' directory into <machine_agent_dir>/monitors/
4. Edit config.yml file in AWSAPIGatewayMonitor and provide the required configuration (see Configuration section).
5. 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.

Configuration

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 config.yml file.

1. If SIM is enabled, then use the following metricPrefix
   metricPrefix: "Custom Metrics|AWS APIGateway"
   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 APIGateway|".

    For example,
    ```
    metricPrefix: "Server|Component:100|Custom Metrics|AWS APIGateway|"
    ```
   

More details around metric prefix can be found here.

2. Provide accessKey(required) and secretKey(required) of our 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 these values,
   extension will use IAM profile to authenticate.

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

3. Provide the list of Api names that needs to be monitored. This list accepts regular expressions.

   apiNames: ["api1", "api2"]
   

Metrics

1. 4XXError - The number of client-side errors captured in a specified period.
2. 5XXError - The number of server-side errors captured in a given period.
3. CacheHitCount - The number of requests served from the API cache in a given period.
4. CacheMissCount - The number of requests served from the back end in a given period, when API caching is enabled.
5. Count - The total number API requests in a given period.
6. IntegrationLatency - The time between when API Gateway relays a request to the back end and when it receives a response from the back end.
7. Latency - The time between when API Gateway receives a request from a client and when it returns a response to the client. The latency includes the integration latency and other API Gateway overhead.

Apart from the above metric, we also have a metric called "API calls", that gives out the number of cloudwatch API calls from the extension.

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

Troubleshooting

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.

Contributing

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

Version

Note: While extensions are maintained and supported by customers under the open-source licensing model, they interact with agents and Controllers that are subject to AppDynamics’ maintenance and support policy. Some extensions have been tested with AppDynamics 4.5.13+ artifacts, but you are strongly recommended against using versions that are no longer supported.