Configuration of AWSAmazonLambdaTest

This test automatically discovers the Lambda functions, monitors the invocations of each function, and in the process, reports latencies and errors/failures in function execution. This enables administrators to quickly and accurately identify slow and/or buggy functions, so that they take those functions and their codes up for closer review and fine-tuning.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify the host for which the test is to be configured in the HOST text box.

• To monitor an Amazon EC2 instance, the eG agent has to be configured with the AWS ACCESS KEY and AWS SECRET KEY of a user with a valid AWS account. For this purpose, we recommend that you create a special user on the AWS cloud, obtain the access and secret keys of this user, and configure this test with these keys. The procedure for this has been detailed in the Obtaining an Access key and Secret key topic. Make sure you reconfirm the access and secret keys you provide here by retyping it in the corresponding CONFIRM text boxes.

• In some environments, all communication with the AWS EC2 cloud and its regions could be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the PROXY HOST and PROXY PORT parameters. By default, these parameters are set to none, indicating that the eG agent is not configured to communicate via a proxy, by default.

• If the proxy server requires authentication, then, specify a valid proxy user name and password in the PROXY USER NAME and PROXY PASSWORD parameters, respectively. Then, confirm the password by retyping it in the CONFIRM PASSWORD text box. By default, these parameters are set to none, indicating that the proxy sever does not require authentication by default.

• If a Windows NTLM proxy is to be configured for use, then additionally, you will have to configure the Windows domain name and the Windows workstation name required for the same against the PROXY DOMAIN and PROXY WORKSTATION parameters. If the environment does not support a Windows NTLM proxy, set these parameters to none.

• In the EXCLUDE REGION box, you can provide a comma-separated list of region names or patterns of region names that you do not want to monitor. For instance, to exclude regions with names that contain ‘east’ and ‘west’ from monitoring, your specification should be: *east*,*west*

• By default, the LAMBDA FILTER NAME parameter is set to FunctionName. This means that by default, this test will report metrics for each Lambda function that is in use.

  If required, you can override this default setting by setting the LAMBDA FILTER NAME parameter to one of the following:

  • Version - When you use versioning in AWS Lambda, you can publish one or more versions of your Lambda function. As a result, you can work with different variations of your Lambda function in your development workflow, such as development, beta, and production. Each Lambda function version has a unique Amazon Resource Name (ARN).

    If you want this test to report metrics for every version of every Lambda function, select the Version option.

  • Alias - AWS Lambda also supports creating aliases for each of your Lambda function versions. Conceptually, an AWS Lambda alias is a pointer to a specific Lambda function version. It's also a resource similar to a Lambda function, and each alias has a unique ARN. Each alias maintains an ARN for the function version to which it points.

    Select the Alias option if you want this test to report metrics for each alias that points to a version of a function.

• By default, the DD FOR TOTAL flag is set to No. This means that detailed diagnostics are not reported for the Total lambda functions measure (available only for the Summary descriptor) by default.

  Where numerous Lambda functions are configured, collecting and storing the details of each such function as part of detailed metrics can increase the processing overheads of the eG agent and also consume a significant amount of database space. This is why, the eG agent does not collect detailed statistics for the Total Lambda functions measure by default. However, if the eG agent has enough processing power at its disposal, and a well-sized, well-tuned eG database is in use, then you can set this flag to Yes, so that detailed diagnostics are captured for the Total Lambda functions measure.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.