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

Logstash syslog input shoud use UDP instead of TCP #101

Open
joerg opened this issue Jan 27, 2015 · 4 comments
Open

Logstash syslog input shoud use UDP instead of TCP #101

joerg opened this issue Jan 27, 2015 · 4 comments

Comments

@joerg
Copy link

joerg commented Jan 27, 2015

By default syslog should always use UDP instead of TCP. With TCP the problem is, that if the syslog (logstash) server is unavailable the sending server will start blocking of caching which can be very problematic. This can even crash your whole infrastructure if the logstash server is down for too long.

@patcon
Copy link
Contributor

patcon commented Sep 23, 2015

+1

was just investigating why tcp type instead of logstash:
http://logstash.net/docs/1.3.2/inputs/syslog

@martinb3
Copy link
Contributor

There's definitely some different tolerance for loss of logs across implementations... some people seem to want to never lose logs and bring down the service before they lose logs, and some want to drop logs and always keep the service up.

We defaulted to the one that doesn't lose logs, but perhaps we should provide an option?

@patcon
Copy link
Contributor

patcon commented Sep 23, 2015

Ah, that makes sense. syslog input starts listeners for udp and tcp fwiw

@martinb3
Copy link
Contributor

Indeed 👍

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

No branches or pull requests

3 participants