A high volume of production errors in logs makes it harder for deployers (and teams with new code in production) to tell if new code is broken.
I believe that error logs should typically be quiet enough that any real error stands out immediately. To state this another way: Even if an error in production doesn't manifest as breakage for an end-user of the software, it should still be treated as broken code in production because it meaningfully reduces our ability to detect and triage things that do break for users.
How can we improve our logspam situation in both technical and social terms? What are teams already doing about the problem that I'm just not aware of?