-
Notifications
You must be signed in to change notification settings - Fork 48
[BUG] do not output error message for connections closed due to timeout #241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
rdner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking this PR until we find a better solution. See elastic/beats#40824 (comment)
42cede5 to
8e14431
Compare
8e14431 to
bd5ba8d
Compare
💚 Build Succeeded
History
|
rdner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After some investigation with @khushijain21 we didn't find a better solution other than skipping the log entries for the closed connection error.
This error is still returned and should be handled and logged by the consumer of loggingConn type.
What does this PR do?
This PR fixes elastic/beats#40824
Why is it important?
Avoid polluting log with
use of closed connectionerrors due toidleConnectiontimeoutChecklist