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.
The following screenshot shows a notification issued by RDS:
And also two screenshots of CodePipeline notifications:
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 RDS
- 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:
https://api.marbot.io/v1/endpoint/$endpoint-ID/alert - notification:
https://api.marbot.io/v1/endpoint/$endpoint-ID/notification
Take your AWS monitoring to a new level! Chatbot for AWS Monitoring: Configure monitoring, escalate alerts, solve incidents.
Michael Wittig
Consultant focusing on Amazon Web Services (AWS). Entrepreneur building marbot.io. Author of Amazon Web Services in Action, Rapid Docker on AWS, and cloudonaut.io.
You can contact me via Email, Twitter, and LinkedIn.
Published on and updated on
