3 ms·
It kind of depends on the types of errors. Do you need to do anything about every connection reset by peer error for web clients? Could you even if you tried?
by toast0 4y ago
It kind of depends on the types of errors. Do you need to do anything about every connection reset by peer error for web clients? Could you even if you tried?
OTOH, the correct number of connection reset by peer errors between your web servers and your database servers is likely zero, and there may be something to do.
- beachy 4y agoThere are different types of errors as you rightfully point out. Peer resets for web clients are (typically) caused by environmental factors outside the hosts control. It would make sense to group then and monitor then in the aggregate - if there's a surge of 200% then some investigation might well be warranted. I will however guarantee that the author does not mean that they actually look at every peer reset individually. Broken database connections - yes, a code red and they must be examined urgently. The whole point is to classify your errors, and especially to know when a new class of error had been seen.