An AWS Lambda function is intermittently failing several times a day. A SysOps administrator must find out how often this error has occurred in the last 7 days.
Which action will meet this requirement in the MOST operationally efficient manner?
An AWS Lambda function is intermittently failing several times a day. A SysOps administrator must find out how often this error has occurred in the last 7 days.
Which action will meet this requirement in the MOST operationally efficient manner?
The most operationally efficient manner to find out how often the AWS Lambda function error has occurred in the last 7 days is to use Amazon CloudWatch Logs Insights. CloudWatch Logs Insights is designed to help you easily search and analyze log data from AWS services, including AWS Lambda, without requiring extensive setup or configuration. It provides a powerful query language, real-time log data analysis, and direct access to your log groups. This direct approach is simpler and more effective than setting up additional services like Amazon Athena or Amazon OpenSearch Service to accomplish the same goal.
Voting for C! https://aws.amazon.com/blogs/compute/operating-lambda-using-cloudwatch-logs-insights/
why not A : Using Amazon Athena to query CloudWatch logs could work, but it introduces additional complexity by setting up and managing Athena. why not B : Querying AWS CloudTrail logs is primarily for tracking API activity and resource changes. It might not provide the same level of visibility into Lambda function errors
C. Use Amazon CloudWatch Logs Insights to query the associated Lambda function logs.
C is the answer
Ans: C
Well it doesnt makes sense to be A since it would be needed to configure a Bucket for the logs plus setting up Athena for querying the Bucket. I'm going for C.
ccccccc
C .
Log insights is the easiest way to access this info. Athen doesn't query CW logs directly. Using this will require exporting CW logs, uploading to S3, creating a table which is least optimal solution. Therefore C