![]() It’s config file: region: us-east-1 set_timestamp: false delay_seconds: 60 metrics: - aws_namespace: AWS/SES aws_metric_name: Send - aws_namespace: AWS/SES aws_metric_name: Delivery - aws_namespace: AWS/SES aws_metric_name: Bounce - aws_namespace: AWS/SES aws_metric_name: Complaint - aws_namespace: AWS/SES aws_metric_name: Reputation.BounceRate - aws_namespace: AWS/SES aws_metric_name: Reputation.ComplaintRate So, for SES we will use a common exporter, see the Prometheus: CloudWatch exporter - сбор метрик из AWS и графики в Grafana ( rus). Usually, we are using the yet-another-cloudwatch-exporter, but for the AWS SES metrics it displayed garbage, on its Github Issues questions are answered very rarely, and in general, for now, it seems like an abandoned project. Prometheus CloudWatch Exporter configuration In our case, we will collect them to a Prometheus instance which will then use its Alertmanager to send alerts to the Opsgenie, and Opsgenie will forward them to our Slack. There are two ways for alerting: by using AWS CloudWatch Alerts and SNS, see Creating reputation monitoring alarms using CloudWatch, or by collecting those metrics to an external monitoring system. ![]() (at the end of this post it will grow to 18% - we’ve got an additional 4% per day) Complaints: an email was delivered to the recipient’s mailbox, but was marked as spamĪlso, we have two additional recalculated metrics here for the Bounce and Complaint - Reputation.BounceRate and Reputation.ComplaintRate.Īt this moment, our Reputation.BounceRate = 0.1432, i.e 14%:.Bounces: a recipient’s mail server refused to accept an email (counted as hard bounces).Deliveries: total emails being delivered to a recipient’s mailbox.AWS SES CloudWatch metricsįor alerting we can use AWS CloudWatch metrics for AWS SES: Soft bounce: is when a recipient’s email server accepted an email but wasn’t able to deliver an email to a user’s mailbox, for example, due to disk quotas for a user or because of an email’s sizeĬomplaint rate is counted when a recipient explicitly notifies that he doesn’t want to get an email from the sender, for example by pressing the “Spam” button in its mail client or by sending abuse to the AWS SES.This can happen due to a wrong email address, its domain on the remote server, or if the server can’t accept new emails at all Hard bounce: is when a recipient’s email server refuses to accept an email at all.Here we’ve got the 0.1% - great result if it could be real for us :-) Hard and Soft BounceĪlso, the Bounce rate is distinguished as hard and soft ratings. Bounce rateīounce rate defines which part of recipients didn’t receive emails, see Bounce Rate. Let’s see what are Bounce and Compliant ratings, and then will configure Prometheus Alertmanager to send an alert if they will reach 5% of the Bounce rating and over 1% of the Compliant rate.Ĭheck the What can I do to minimize bounces? for some additional info. ![]() In case of its high ratings, remote email servers can stop accepting new emails from IPs of AWS by marking them as “spam”, so AWS is closely monitoring those indicators. ![]() Prometheus CloudWatch Exporter configurationĪWS can block an SES account because of a high Bounce rate or Complaint rate.In this post, we will take an overview of the Bounce and Complaint rating for emails in general, and then will configure AWS SES monitoring and alerting with hAWS CloudWatch and Prometheus. After we’ve connected AWS Tech Support, they enabled it back, but we must solve the issue asap, and have to monitor AWS SES Bounce rate in the future to avoid such situations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |