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

Do we need beaver/logstash-forwarder? #14

Open
martinb3 opened this issue Aug 25, 2014 · 1 comment
Open

Do we need beaver/logstash-forwarder? #14

martinb3 opened this issue Aug 25, 2014 · 1 comment

Comments

@martinb3
Copy link
Contributor

https://github.com/elasticsearch/logstash-forwarder
https://github.com/josegonzalez/beaver

I think we'll support the java agent to start and consider these other two later.
@jujugrrr
Copy link
Contributor

We need a logstash-agent, the java one provided by logstash is pretty cool performs quite well and have some many options (input/output/filters etc...) if we want something simpler without Java, then logstash-fowarder/beaver might be a good alternative

@martinb3 martinb3 changed the title Do we need lumberjack/logstash-forwarder? Do we need lumberjack/logstash-forwarder/beaver? Sep 16, 2014
@martinb3 martinb3 changed the title Do we need lumberjack/logstash-forwarder/beaver? Do we need beaver/logstash-forwarder/beaver? Sep 18, 2014
@martinb3 martinb3 changed the title Do we need beaver/logstash-forwarder/beaver? Do we need beaver/logstash-forwarder? Sep 22, 2014
martinb3 added a commit that referenced this issue May 1, 2015
@martinb3
Remove lumberjack as default for logstash
e19dfc7 
- The lumberjack protocol will no longer be the default for Logstash to communicate, due to hosted chef changes and golang runtime SSL changes (fixes #56, #14)
- Don't test the lumberjack protocol with the server install by default, removes lumberjack test suite in .kitchen.yml
- Default to tcp/udp for communication between logstash instances, add flag:
  `node['elkstack']['config']['agent_protocol'] = 'tcp_udp' # could also be lumberjack`
- Don't try to load lumberjack secrets by default for agent, don't fail if they aren't present (rename recipes/_secrets.rb -> recipes/_lumberjack_secrets.rb)
- elkstack::acl recipe changes to support tcp/udp communication
- add logstash configs for tcp/udp communication
- remove tests for lumberjack.key/crt now from default test suites
- remove extra data bags with lumberjack keypairs
@martinb3 martinb3 mentioned this issue May 1, 2015
Merged
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
@martinb3 @jujugrrr