Refactor severity to use monitor thresholds#17
Refactor severity to use monitor thresholds#17lngarrett wants to merge 2 commits intotrueaccord:masterfrom
Conversation
|
After some experimentation, I think monitors would still benefit from being marked as I'm envisioning the teams config would look like this: The idea here is that on a |
|
I'm also looking to get this for my team. Is there anything missing in order to merge this? It doesn't seem entirely backward compatible, but works MUCH better for our workflow. |
On our team we wanted a way to centralize the management of both our monitors, but also the conditional notifications in the monitors' messages. This PR ties a team's severity notifications to the alert threshold. Instead of setting a monitor to have a certain severity, the message will have conditional blocks containing the appropriate notification channels based on the threshold of the alert. I also put all notifications into a
is_recoveryblock so that alerts auto resolve as expected.Nothing new is required in the config, and all fields are optional.
Example message: