-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
fix(input.redis): Discard invalid errorstat lines #15312
fix(input.redis): Discard invalid errorstat lines #15312
Conversation
8f3b59b
to
f0f9981
Compare
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.
Thanks for your contribution @nicois! I would prefer to add errors instead of debug logs as this simplifies code, make users more aware and is discoverable on the database side when using the inputs.internal
plugin.
What do you think?
3ef2f94
to
3c0c0ae
Compare
…#15311) Some badly-behaved sources (such as dragonfly) may send error messages which are not in the expected format. If errorstat lines are found which do not include an `=` sign, silently discard them. Somewhere between 1.26 and 1.28.5, a change was made which caused such missing '=' symbols to cause a panic. In addition to ignoring such entries, add debug-level logging for this and a similar problem, where the errorstat values are not base-10.
3c0c0ae
to
86946df
Compare
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
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.
LGTM. Thanks @nicois!
(cherry picked from commit 7f4d27d)
Summary
Some badly-behaved sources (such as dragonfly) may send error messages which are not in the expected format. If errorstat lines are found which do not include an
=
sign, silently discard them.Somewhere between 1.26 and 1.28.5, a change was made which caused such missing '=' symbols to cause a panic.
In addition to ignoring such entries, add debug-level logging for this and a similar problem, where the errorstat values are not base-10.
Checklist
Related issues
resolves #15311