made SSLKey and SSLCrt optional in the lumberjack input#9
Open
rrichardson wants to merge 2 commits into
Open
Conversation
Contributor
|
Thanks for the PR. My understanding is that Logstash has insisted that TLS be mandatory: elastic/logstash-forwarder#5 (comment) Is this no longer true for Filebeat? |
Author
|
I'm not sure if I care to follow the recommendation, myself. I'm using the (official?) elasticsearch golang APII to log directly from my services. https://github.com/elastic/go-lumber . It doesn't use TLS. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Made SSLKey and SSLCrt optional in lumberjack input. If they are absent from the config, it will listen via TCP instead of TLS.
For my use case, I am transmitting only on localhost, as I have 1 logzoom daemon per server, so I don't need the overhead of TLS.