Skip to content

Don't send read/write errors to Sentry

Mikhail Mazurskiy requested to merge ash2k/no-sentry-write-err into master

Currently there are quite a few Proxy failed to write response to client: write tcp x.x.x.x:8154->x.x.x.x:58075: i/o timeout errors. Also a single Proxy failed to read request body from client: read tcp x.x.x.x:8154->x.x.x.x:63017: i/o timeout.

Edited by Mikhail Mazurskiy

Merge request reports