marbot

Configure AWS monitoring, receive alerts, solve incidents. Available for Slack and Microsoft Teams.

[marbot @marbot_io]

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

[marbot @marbot_io]

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 🧵

[marbot @marbot_io]

Setup: You can connect your AWS account with marbot right from an alert or notification.

[marbot @marbot_io]

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.

[marbot @marbot_io]

A VPC Nat gateway can process up to 100 Gbit/s. Learn how to monitor NAT gateways with CloudWatch: https://t.co/wsozWLLdBP

[marbot @marbot_io]

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.

[marbot @marbot_io]

A VPC interface endpoint can process up to 100 Gbit/s. Learn how to monitor interface endpoints with CloudWatch: https://t.co/NQzxE99Xbl

[marbot @marbot_io]

⚠️ Some customers may experience issues while using marbot due to a Slack incident related to interactive messages (see https://t.co/xLVyiRyDsG).

[marbot @marbot_io]

Learn how: https://t.co/wsozWLLdBP

[marbot @marbot_io]

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!

[marbot @marbot_io]

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 @marbot_io]

🚨 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.

[marbot @marbot_io]

@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!

[marbot @marbot_io]

@tessiselated We are reprocessing a backlog of messages. Things should be back to normal in minutes.

[marbot @marbot_io]

The Slack API is up and running again. Everything working fine.

[marbot @marbot_io]

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.