-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add TCP Support #1
Comments
+1 Gelf-rb starts support of gelf tcp. Please suggest extending! |
this looks like a simple change:
|
+1 |
+1... This is a must for our environment. Please bring this new feature in the next release. |
FYI... |
Are there any plans to work on this enhancement? TCP is a must for deploying a scalable Graylog cluster in AWS, since AWS elastic load balancers do not support UDP |
Still no TCP in 2017?! So TCP support in Graylog2/gelf-rb has been developed all in vain, indeed. |
this can be closed due to #19 |
For those landing on this from Google, the TCP option for logstash's gelf output plugin has been available since v3.0.0 of the plugin. There's a (currently undocumented) option you can add to the output plugin |
I hope someday someone will fine the time and update 'docs/index.asciidoc' with this hidden protocol => "tcp" option. |
Adds documentation for the `protocol` option, which allows a user to configure this plugin to output via the TCP transport protocol instead of the default UDP, which was added in 3.0.0 via logstash-plugins#19 Resolves: logstash-plugins#1
Adds documentation for the `protocol` option, which allows a user to configure this plugin to output via the TCP transport protocol instead of the default UDP, which was added in 3.0.0 via logstash-plugins#19 Resolves: logstash-plugins#1
Adds documentation for the `protocol` option, which allows a user to configure this plugin to output via the TCP transport protocol instead of the default UDP, which was added in 3.0.0 via logstash-plugins#19 Resolves: logstash-plugins#1
migrated from: https://logstash.jira.com/browse/LOGSTASH-780
Graylog 0.10 starts supporting TCP transport for gelf.
Since this enables safer transport than UDP, I suggest extending the gelf input/output with a TCP option.
The text was updated successfully, but these errors were encountered: