In newest AppBeat version 1.7.0 you can now define quiet hours for your users, services and/or third-party integrations (I will refer to these as “resources”).
Quiet hours are recurring time periods during which alerts (outgoing notifications) are muted for selected resource(s). Quiet hours does not affect monitoring, just notifications. This means that you will always be able to check log entries, even during effective quiet hours.
You can access this new feature from “Alerting” module and by clicking “Quiet hours” tab as shown below:
When you click “Add quiet hours for” button for specific resource, you will be presented with dialog similar to this:
You can add multiple quiet hours for same resource, AppBeat engine will always aggregate those entries while determining if quiet hour is effective or not.
Here are some use case examples:
- you have service which is not operational 24/7 - now you can simply set quiet hours when service is not active so you don’t receive any alerts
- you have recurring (nightly) updates and you want to mute alerts during this period
- you don’t want to receive alerts for less important service(s) during weekend
- your team member goes on vacation or sick leave and you don’t want to bother him/her with outage alerts
- some of your team members receive alerts only during working hours (and you have dedicated team for 24/7 operations)