Recipes for S3 monitoring

0

Are there any recommendations / recipes for S3 Request metrics monitoring?

Customer wants to use CW alarms particularly for the PutRequests, GetRequests, 4xxErrors, and DeleteRequests metrics, the challenge is trying to avoid false positives.

Any advices are appreciated. Thank you

profile pictureAWS
已提問 5 個月前檢視次數 211 次
1 個回答
1
已接受的答案

Are you considering S3 Storage Lens as a source for these metrics? Once you will be able to publish these statistics to CloudWatch for PutRequests, GetRequests, 4xxErrors, and DeleteRequests metrics, you will be able to create your alarms. What scenarios they want the Alarm to be triggered for on each of these API requests? Anomalies?

profile pictureAWS
AmerO
已回答 4 個月前
  • Haven´t considered CW Storage Lens, only S3 Request Metrics, I will take a look on that. The main objective is to establish a baseline for normal 4xx error rates, and then investigate anomalies, which could be a sign of a configuration problem, networking issue, or other performance disruption. They are looking for tips to properly configure alarms thresholds in order to avoid false positives.

  • Sorry, I just updated that. I meant to say S3 Storage Lens. I will say explore anomaly detection as threshold for CloudWatch alarm if they can't come up with baseline threshold. For errors, I will start by visualizing the trend, Statistics and percentiles. They can consider metric math for that. I will say start by analyzing the current baseline as ideal performance, and then determine a value that drifts from the baseline. However, we have some recommendations for thresholds based on different metrics here: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.html

  • Thanks, that helps a lot. I will take a look.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南