Dynamic Alerts using PlayBooks
Receive alerts for more than just static thresholds
Objective
Businesses need more than just static thresholds in their alerts to tell if something is wrong. While most monitoring tools and their alerting features offer configuring of a single threshold against a metric, in reality an engineer is looking for more complex rules like:
- Having different threshold based on seasonality of your product usage & business
- Doing more checks (in logs / DB) other than just the concerned metric before needing to be notified
- Comparing the metric against past behaviour and only be notified when its breaking the trend
Doctor Droid's dynamic alerting features cater to these needs and helps a developer remove false positives from landing in their inbox / channel.
How it works?
The Dynamic Alerting feature is part of the Playbooks Open-Source project, in fact it is powered via Playbooks in the backend. Here is how you can setup your first Dynamic Alert.
-
Clone the repo, deploy it using Docker-compose or Helm.
-
Add your metric data source. The project supports plenty of popular metric sources.
-
Go to Dynamic alerts.
-
Add the metric query from your data source
-
Add different thresholds against different time schedules. You can add a schedule with flexibility ranging from selecting day of the month to selecting hour of the day (in UTC).
-
Add a notification destination and save it. Now your dynamic alert is setup and is being run for different thresholds at different times.
Note :- Here is a guide on how to setup your Slack app for this integration and bring those channel names here
Updated 4 months ago