@jijiki I'd recommend reframing this task to a problem statement, maybe with title 'high volume of unactionable alerts for oncall'?

And in the description or as comments, adding more color to size the problem: anecdotal examples from recent incidents, what do we see as the most 'unactionable' (wrong threshold, confusing name/description in the alert, missing runbook, irrelevant alerts).

@hnowlan if you have ideas on how to measure that

For example, today there was a page for Mathoid, with two alert, one for the blackbox[[ https://grafana.wikimedia.org/goto/P-h7Dq4Dg?orgId=1 | test ]] and another for OpenAPI/Swagger endpoints being unhealthy , and then hen we got the ATS alert on top of that, since the real cause was a scraper. Additionally, honestly, I wouldn't remember off the top of my head that its URL path contains media/math/, which would have made pattern matching so much easier and faster.

In T410038#11515987, @MLechvien-WMF wrote:

@jijiki I'd recommend reframing this task to a problem statement, maybe with title 'high volume of unactionable alerts for oncall'?

And in the description or as comments, adding more color to size the problem: anecdotal examples from recent incidents, what do we see as the most 'unactionable' (wrong threshold, confusing name/description in the alert, missing runbook, irrelevant alerts).

I will work the description again, I agree that it is a bit broad, and we can later discuss about priority

After presentation of Denisse last week, should we try to use their tool (and make feature requests if we miss something important)?