-
Notifications
You must be signed in to change notification settings - Fork 979
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 graylog connecting issue #1506
Conversation
Oh, gelf-rb/issues/63 may be still brocker. |
For graylog, fluent-plugin-json-in-json-2 depends on yajl-ruby... |
Thanks. I see... |
TODO: eliminate yajl-ruby (yajl/json_gem) |
Purge yajl/json_gem explicitly from image? |
The issue of |
Closes: fluent#1479 Feedback from @mszyzdek ref. fluent#1479 (comment) * graylog flavour of fluentd-kubernetes-daemonset uses gelf 3.0.0 and this version of gelf gem has Fixnum in code, graylog-labs/gelf-rb@7cc3cbb * in ruby 3.2 Fixnum was removed after previous deprecation in version 2.4 https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ * ruby in newest fluentd was upgraded to 3.2 fluent/fluentd-docker-image@4f1d5e8 so it also happened in fluentd-kubernetes-daemonset * gelf 3.0.0 cannot work with ruby 3.2+ so we can see sad error on container start NOTE: Even though gelf was updated to 3.1.0, still it has problem with reloading Fluentd configuration with SIGUSR2. This is known issue since Fluentd 1.8.0. ref. fluent/fluentd#2709 Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
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! LGTM.
Although gelf 3.1.0
has a remaining issue, we should update it because the impact is limited to not being able to SIGUSR2
to reload the config.
Thanks, after #1507 was merged, let's ship it. |
Closes: #1479
Feedback from @mszyzdek
ref. #1479 (comment)