Today we launch notifications

Michael Wittig – 31 Jan 2020 (updated 20 Apr 2020)

For many years now, marbot sends alerts to your Slack workspaces. Alerts include RDS disk space warnings, excessive CPU utilization reported by CloudWatch, broken CodePipeline executions, and many more. Our customers have asked us also to support “alerts” that are not urgent. Today, we launch notifications. Notifications are for events that do not require immediate attention.

Today we launch notifications

The following screenshot shows a notification issued by RDS:

RDS cross AZ failover notification

And also two screenshots of CodePipeline notifications:

CodePipeline Approval notification

CodePipeline Stage Execution notification

Notifications differ from Alerts in three ways:

Feature Notification Alert
Acknowledge / Close no yes
Escalation always send to the channel (no mentions) Full escalation chain
Aggregation 1 minute 7 days

Supported Sources for Notifications:

  • AWS Elastic Beanstalk
  • AWS CodePipeline
  • AWS Backup
  • Amazon ElastiCache
  • Amazon Linux AMI update
  • BitBucket

marbot separates alerts from notifications automatically based on the content of an event. If you need full control, you can define the severity by using one of those two URLs:

  • alert:$endpoint-ID/alert
  • notification:$endpoint-ID/notification
Michael Wittig

Michael Wittig

Consultant focusing on Amazon Web Services (AWS). Entrepreneur building Author of Amazon Web Services in Action, Rapid Docker on AWS, and

You can contact me via Email, Twitter, and LinkedIn.

Published on and updated on

marbot teaser

Chatbot for AWS Monitoring

Configure monitoring for Amazon Web Services: CloudWatch, EC2, RDS, EB, Lambda, and more. Receive and manage alerts via Slack. Solve incidents as a team.

Add to Slack
Microsoft Teams
Add to Teams