Feature Request: Add Alert Processing Rules

[brmcmill]

I think adding some Alert Processing Rules may help with facilitate the busy/noise some of these alerts will have especially for those environments that are used for Testing/Dev. We don't want immediately for things to suppress, but have an option to keep things less noisy where possible so customers can efficiently read/react to the alerts that come in.

[jamasten]

I wonder if it's worth removing the dimensions on this alert. That way if there's one or more issues, you only receive one alert until the issue is resolved. The customer would click the query in the email to see which host has an issue. Does that make sense?

[brmcmill]

It does, we just really need something that is efficient and less busy. I had to disable a few alerts because they were spitting out too much information. To me they are warranted, but the customer was overthrown with too much to filter through.

[brmcmill]

Right now, we changed the Aggregation to 15 minutes instead of 5. Will continue to monitor.

@JCoreMS / @jamasten

[brmcmill]

Hey @JCoreMS / @jamasten , we're still running into the CPU/Memory alerts going crazy during builds. We're going to make sure these are disabled going forward when we're doing builds, then renable after. Is there anything else we can probably look at adjusting?