DVA-C02 · Question #741
A developer needs to troubleshoot errors within Amazon CloudWatch Logs log data. The logs record attempts by an AWS Lambda function to connect to a REST-based service that a third party hosts. Each…
The correct answer is B. Use CloudWatch Logs Insights to parse the log data. Filter results that match the range of 500. HTTP 500-level status codes indicate server-side errors, which are problems on the third party's side. Using CloudWatch Logs Insights, the developer can filter logs by 500 status codes, then use the count and bin() functions to generate a daily summary of those failed requests…
Question
A developer needs to troubleshoot errors within Amazon CloudWatch Logs log data. The logs record attempts by an AWS Lambda function to connect to a REST-based service that a third party hosts. Each line of the log data displays the HTTP verb used, the URL accessed, and the HTTP status code. The developer needs to create a summary of requests that failed because of a problem on the third party's side. The developer must produce the summary every day. Which solution will meet these requirements?
Options
- AUse CloudWatch Logs Insights to parse the log data. Filter results that match the range of 400
- BUse CloudWatch Logs Insights to parse the log data. Filter results that match the range of 500
- CUse CloudWatch Contributor Insights to parse the log data. Map the status code data to a field.
- DUse CloudWatch Contributor Insights to parse the log data. Map the status code data to a field.
How the community answered
(35 responses)- A3% (1)
- B74% (26)
- C9% (3)
- D14% (5)
Explanation
HTTP 500-level status codes indicate server-side errors, which are problems on the third party's side. Using CloudWatch Logs Insights, the developer can filter logs by 500 status codes, then use the count and bin() functions to generate a daily summary of those failed requests. This provides the required insight with minimal setup.
Community Discussion
No community discussion yet for this question.