AWS Lambda¶

The displayed Metrics of AWS Lambda include cold start time, execution time, concurrent executions, and memory usage, which reflect the response speed, scalability, and resource utilization of Lambda functions.

Configuration¶

Install Func¶

It is recommended to activate the Guance integration - Extensions - DataFlux Func (Automata): all prerequisites are automatically installed, please proceed with the script installation.

If you deploy Func manually, refer to Manual Func Deployment

Install Script¶

Note: Please prepare the required Amazon Cloud AK in advance (for simplicity, you can directly grant CloudWatch read-only permission CloudWatchReadOnlyAccess)

Automata Script Activation¶

1. Log in to the Guance console
2. Click the 【Integration】 menu, select 【Cloud Account Management】
3. Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured the cloud account information, skip this step.
4. Click 【Test】, and if the test is successful, click 【Save】. If the test fails, check the relevant configuration information and retest.
5. Click 【Cloud Account Management】, and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page.
6. Click the 【Integration】 button on the cloud account details page, find AWS Lambda under the Not Installed list, and click the 【Install】 button to pop up the installation interface for installation.

Manual Script Activation¶

1. Log in to the Func console, click 【Script Market】, enter the official script market, and search for: guance_aws_lambda

2. Click 【Install】, then enter the corresponding parameters: AWS AK ID, AK Secret, and account name.

3. Click 【Deploy Startup Script】, the system will automatically create a Startup script set and configure the corresponding startup script.

4. After activation, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】 to execute it immediately without waiting for the scheduled time. After a while, you can view the execution task records and corresponding logs.

Verification¶

1. Confirm in 「Management / Automatic Trigger Configuration」 whether the corresponding task has the automatic trigger configuration, and you can also check the corresponding task records and logs for any anomalies.
2. In Guance, check in 「Infrastructure / Custom」 whether the asset information exists.
3. In Guance, check in 「Metrics」 whether there is corresponding monitoring data.

Metrics¶

After configuring Amazon CloudWatch, the default Measurement is as follows. More Metrics can be collected through configuration:

Amazon CloudWatch Lambda Metrics Details

Invocation Metrics¶

Performance Metrics¶

Performance Metrics provide detailed information about the performance of individual function invocations. For example, the Duration metric indicates the amount of time (in milliseconds) that the function spends processing an event. To understand how quickly your function processes events, use the Average or Max statistics to view these Metrics.

Concurrency Metrics¶

Lambda reports concurrency Metrics as a total count of instances processing events across functions, versions, aliases, or AWS regions. To see how close you are to the concurrency limit, use the Max statistics to view these Metrics.

Asynchronous Invocation Metrics¶

Asynchronous invocation Metrics provide detailed information about asynchronous invocations from event sources and direct invocations. You can set thresholds and alarms to notify you of certain changes. For example, when the number of events queued for processing unexpectedly increases (AsyncEventsReceived). Or, when an event waits a long time to complete processing (AsyncEventAge).

Object¶

The collected AWS Lambda object data structure can be seen in 「Infrastructure - Custom」.

{
  "measurement": "aws_lambda",
  "tags": {
    "account_name"      :"AWS_Lambda",
    "class"             :"aws_lambda",
    "cloud_provider"    :"aws",
    "FunctionName"      :"dataflux-alb",
    "name"              :"dataflux-alb",
    "PackageType"       :"Zip",
    "RegionId"          :"cn-northwest-1",
    "RevisionId"        :"5e52ff51-615a-4ecb-96b7-40083a7b4b62",
    "Role"              :"arn:aws-cn:iam::294654068288:role/service-role/s3--xxxx-role-3w34zo42",
    "Runtime"           :"python3.7",
    "Version"           :"$LATEST"
  },
  "fields": {
    "CreatedTime"         : "2022-03-09T06:13:31Z",
    "ListenerDescriptions": "{JSON Data}",
    "AvailabilityZones"   : "{Availability Zone JSON Data}",
    "message"             : "{Instance JSON Data}"
  }
}

Note: The fields in tags and fields may change with subsequent updates.

Tip 1: The value of tags.account_name is the instance ID, used as a unique identifier.