This is an interesting suggestion though I think I need to understand the use case better. My understanding is that when an alert is resolved it disappears, so wouldn't that mean the bug that was just linked would disappear as well? 

I assumed that the data from SoM was used for analytics after the fact, like to figure out what sorts of issues cause the most problems.

If not, then I should just be clicking on the Resolve button when I know there's an outage.

ketakid, are we trying to use SoM like annotator, or just as a tool for gardener?

(Background: On Chrome OS we're supposed to use a tool called "annotator" to note why builds failed. Lots of people don't have time to do it. It would be cool if we could get that information out of SoM. https://chromiumos-build-annotator.googleplex.com/build_annotations/builds_list/master-chromium-pfq/ )

Yeah I think partly we are trying to make the annotation process a lot less cumbersome than it is today. So yes, SOM could be used as an annotator just an easy one. We are not completely there in terms of functionality but getting there.

Yeah, the thought is that we'd have recently resolved which would serve for grouping with recent bugs, and also be used as a sheriff report/hand-off from week to week.  Ideally this ends up in our annotations database for long term record keeping.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot