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.

Sign up for GitHub

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

Jump to bottom

Add an option to support plain TCP #14

Open
ph opened this issue Oct 6, 2015 · 1 comment
Open

Add an option to support plain TCP #14

ph opened this issue Oct 6, 2015 · 1 comment

Comments

@ph
Copy link
Contributor

ph commented Oct 6, 2015

The input lumberjack allow us to disable SSL and the output should expose similar option.
@ph ph mentioned this issue Oct 6, 2015
Closed
@richard-mauri
Copy link

Elastic recommends logstash/lumberjack out to logstash/beats input.
The logstash/lumberjack input is deprecated.

Why does logstash/lumberjack out require ssl_cert? (It fails if that field is not efined)
The logstash beats/input does have an ssl_cert and ssl_key and ssl_verify:: none
A filebeat to logstash/beats input does not need an ssl_cert.
In my case, there is trouble distributing the lumberjack.crt (poor PKI infa).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ph @richard-mauri