Use Slack or Microsoft Teams to configure monitoring for Amazon Web Services: CloudWatch, EC2, RDS, EB, Lambda, and more. Receive and manage alerts in your chat tool. Solve incidents as a team. Try it for free https://t.co/obAMVKmBY6
Big update ๐ CloudWatch graphs and CodePipeline approval are now available. Learn more about the details and the steps to enable the optional new features. A thread ๐งต
Soon you'll be able to mute alerts and notifications! We are looking for beta testers who can give us early feedback. Please contact us via direct message for more information.
Many AWS VPC designs make use of private subnets. To communicate with AWS APIs, you either need a NAT gateway or VPC endpoints. Both options have a catch. The traffic they can process is limited. Learn how to monitor the bottleneck.
A VPC NAT gateway is a finite resource that can be exhausted. Thatโs why you need to add monitoring to be alerted if the NAT gateway gets a bottleneck before prod is down!
Seems like this was a temporary issue only. Things are working smoothly again! marbot for Slack did already catch up and delivered all alarms and notifications.
๐จ marbot for Slack cannot deliver alarms and notifications to some channels right now due to a -hopefully small- outage of an AWS service. We are investigating the issue and will keep you posted.
@tessiselated Things are back to normal. Sorry for the interruption. We saw a bunch of issues with AWS Api Gateway yesterday. This caused an issue with our retry code which we fixed. No messages are lost!
I'm currently having troubles with delivering alarms and messages to Slack. Seems like a problem with the Slack API. Will keep you posted and will deliver alarms later.