One caveat to doing this would be that if we are constantly editing the format of alerts, this would be a lot of schema changes. But I think maybe schema changes should mostly be fine since Sheriff-o-Matic generally mainly cares about recent alerts anyways? 

 Issue 737713  has been merged into this issue.

Unassigning myself for now since I probably won't do this in the immediate future. 

Noting though that the schema changes made for alert grouping were a step in this direction (moving each alert into its own entity instead of having a large entity with all alerts). 

I also want to note that at the moment, Sheriff-o-Matic actually only stores the latest version of each alert by key. So the way alerts are stored would have to be adjusted to store a history of past versions of the same alert. 

This is neat because it'd also make it easier to add history features to sheriff-o-matic. For example: 
- a mini chart of when an alert was active vs. resolved
- the ability to view past versions of an alert or alerts which are resolved.
- maybe adjust annotations to be tied to a specific instance of an alert? ie: if the alert gets resolved and then happens again, the annotations get shelved away with the old version of the alert. This would also solve one of the biggest complaints of Sheriff-o-Matic, which is that annotations often apply to old alerts. 

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