You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[CloudTrail Lambda Data Events](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/logging-management-and-data-events-with-cloudtrail.html#logging-data-events)
21
+
*[CloudTrail Lambda Data Events](https://docs.aws.amazon.com/lambda/latest/dg/logging-using-cloudtrail.html#cloudtrail-data-events)
**The AWS Lambda - Request Analysis** dashboard provides deeper insights into the invocations and performance of your AWS Lambda functions.
320
+
**The AWS Lambda - Request Analysis** dashboard provides deeper insights into the invocations, operations, and performance of your AWS Lambda functions.
321
321
322
322
Use this dashboard to:
323
323
* Monitor the invocation of an AWS Lambda function against all other functions.
324
-
* Identify and top callers, top caller types, and top source IPs.
324
+
* Identify the top source IPs.
325
325
* Monitor failed and successful requests by function name to quickly identify when failed requests are occurring.
326
326
* Troubleshoot and investigate individual function requests.
327
-
* Monitor cold start duration for lambda functions.
327
+
* Monitor cold start duration and key operations for lambda functions.
**AWS Lambda - Usage Analysis** dashboard provides insights into function usage by AWS services, user agents, and IAM users.
334
+
**AWS Lambda - Usage Analysis** dashboard offers insights into function usage, including invocations, calling AWS services, user agents, IAM users, and detailed information about function callers.
335
+
336
+
:::note
337
+
This dashboard provides analysis of AWS CloudTrail Data Events. By default, AWS CloudTrail does not log data events. To enable AWS CloudTrail data events, Refer [AWS Lambda Data Event](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/logging-data-events-with-cloudtrail.html#logging-data-events-console)
338
+
:::
335
339
336
340
Use this dashboard to:
337
341
* Audit, monitor, and compare the functions used in your serverless infrastructure.
338
-
* Monitor which AWS services and IAM users are calling individual AWS Lambda functions.
339
-
* Monitor which user agents are being used in Lambda function calls.
342
+
* Monitor which AWS services and IAM users are calling individual AWS Lambda functions.
343
+
* Monitor which user agents are being used in Lambda function calls.
340
344
* Compare data across time to identify any unusual trends.
345
+
* Identify top callers, top caller types.
346
+
* Monitor the invocation of an AWS Lambda function.
* Prioritize the resolution of errors and warnings across all Lambda functions.
352
358
* Monitor the trend for the number of dead letter errors; when a Lambda is unable to write the failed event payload to your function's dead-letter queue.
353
359
* Monitor the trend for the number of Lambda function throttling events; the number of Lambda function invocation attempts throttled due to invocation rates exceeding the configured concurrent limits.
354
-
* Monitor the trend for Iterator Age applicable for your stream-based invocations only. This measures the age of the last record for each batch of records processed. Age is the difference between the time Lambda received the batch and the time the last record in the batch was written to the stream.
360
+
* Monitor the trend for Iterator Age applicable for your stream-based invocations only. This measures the age of the last record for each batch of records processed. Age is the difference between the time Lambda received the batch, and the time the last record in the batch was written to the stream.
361
+
* Monitor the trend for the number of async event drops, This indicates the number of asynchronous invocation requests that were dropped due to internal service errors or exceeding service limits.
362
+
* Monitor the trend for recursive invocation drops, This measures the number of recursive invocation attempts that were dropped to prevent potential infinite loops and unbounded recursion within Lambda functions.
363
+
* Monitor the trend for destination delivery failures, This tracks the number of times Lambda failed to deliver an asynchronous invocation result to a configured destination, such as an SNS topic, SQS queue, or EventBridge.
0 commit comments