I'm not an expert though.
“Don’t worry about it, I don’t think it’s a real issue so we’re just going to ignore it”
Do you think a doctor is more likely to call something "possible cancer" and recommend that you either have a specialist do a biopsy (keeping in mind that many of these will be... hard to reach) or at least have a follow up MRI in 3, 6, 9 months?
Or tell you it's "pretty unlikely to be cancer, I don't think we need to worry about it" and then get sued for 20M when they are wrong about 1 in 100 cases (not to mention missing out on all the potential income from above).
At least in the US, the incentives here are grossly misaligned.
That is exactly why builders focus on owning aligned systems, not depending on broken ones. More on this at foundniche.com
It's probably more accurate to use a software analogy about performance metrics. We measure random request spikes now and again that strain the system. It's probably fine, but later on down the line, something could change that results in an outage during one of these spikes. Do we proactively fix the problem even if no change is expected? Or do we wait till there is definitely a problem before taking action?