Skip to content
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

Closed
talevy opened this issue Feb 6, 2015 · 10 comments
Closed

Add TCP Support #1

talevy opened this issue Feb 6, 2015 · 10 comments

Comments

@talevy
Copy link
Contributor

talevy commented Feb 6, 2015

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.

@florian-asche
Copy link

+1

Gelf-rb starts support of gelf tcp. Please suggest extending!

@runningman84
Copy link

this looks like a simple change:

# old
# @gelf ||= GELF::Notifier.new(@host, @port, @chunksize)
# new
@gelf ||= GELF::Notifier.new(@host, @port, "LAN", { :protocol => GELF::Protocol::TCP })

@rcord02
Copy link

rcord02 commented Feb 24, 2016

+1
would be awesome if this will be availible in the next release!

@danlsgiga
Copy link

+1... This is a must for our environment. Please bring this new feature in the next release.
Also, @runningman84 I've tested the simple change you suggested but it does not work.

@danlsgiga
Copy link

FYI...
graylog-labs/gelf-rb#21

@ghost
Copy link

ghost commented Sep 30, 2016

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

@alpha-centauri
Copy link

alpha-centauri commented Mar 3, 2017

Still no TCP in 2017?! So TCP support in Graylog2/gelf-rb has been developed all in vain, indeed.

@runningman84
Copy link

this can be closed due to #19

@Moeser
Copy link

Moeser commented Oct 24, 2017

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 protocol => "TCP" that switches it to TCP instead of UDP.

@davesave
Copy link

I hope someday someone will fine the time and update 'docs/index.asciidoc' with this hidden protocol => "tcp" option.

yaauie added a commit to yaauie/logstash-output-gelf that referenced this issue Nov 29, 2017
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
yaauie added a commit to yaauie/logstash-output-gelf that referenced this issue Nov 29, 2017
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
yaauie added a commit to yaauie/logstash-output-gelf that referenced this issue Nov 29, 2017
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
@jsvd jsvd closed this as completed in #30 Dec 22, 2017
jsvd pushed a commit that referenced this issue Dec 22, 2017
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 #19

Resolves: #1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants