Counterpoint: my team at Google did desire to read every single error, but still had SLOs and error budgets. In fact, there was a tool specifically for finding

Counterpoint: my team at Google did desire to read every single error, but still had SLOs and error budgets. In fact, there was a tool specifically for finding and aggregating unique errors so that they could be made into issues. Granted, in practice, that doesn't mean we fixed every single error, but I think that there's no reason to assume "read every single error" conflicts in any way with the typical SRE practices. I'd argue you actually would be doing yourself a disservice to throw away all of the SRE wisdom over this; measuring things quantitatively is definitely not a waste of time.