-
Notifications
You must be signed in to change notification settings - Fork 83
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
file beat Alpha (5.0) #61
Comments
@osmancis you can use the As for use, v5 largely extends syntax. This cookbook doesn't yet support the extended features of 5.0 in the LWRPs (e.g. no JSON input for prospectors), but should work fine if your only use case for 5 is kafka output. If you're not in a place to add a pull request enabling them, you can always simply use the The filebeat output configuration is not restrictive (nor is any other part of I doubt you'll have any issues using the cookbook with 5 here. I'll try to send in a PR to support some of the newer parameters if I have time this week. |
@osmancis Currently beats # yum search filebeat --show-duplicate
Loaded plugins: priorities, update-motd, upgrade-helper
193 packages excluded due to repository priority protections
=========================================================================================================== N/S matched: filebeat ============================================================================================================
filebeat-1.0.0~beta4-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.0.0~rc1-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.0.0~rc2-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.0.0-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.0.1-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.1.0-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.1.1-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.1.2-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.2.0-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.2.1-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.2.2-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.2.3-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch.
filebeat-1.2.3-1.x86_64 : Sends log files to Logstash or directly to Elasticsearch. Perhaps adding an attribute to skip package install via this cookbook could be useful when using wrapper cookbook to install beats I will also give it a try to add support for |
@vkhatri Actually it is available via yum; you just need to use the docs that I linked to and set the repository parameter within the cookbook. They're using an alternate repo for alpha releases.
|
@bradq For some reason, it did not work for me. Does it still work for you? |
This is not working for me either, unfortunately. I can't seem to find the right repo. Added this as
Then I did a But it seems that only Kibana is avaible in the repo:
Since I'm using JSON logging, I need a 5.x version of Filebeat, but I can't think of any way to install it with this recipe. |
@chopmo @vkhatri Sorry for the delayed response...I'm in a new job that doesn't use EL or Filebeat. I'll validate these in a few hours and get back to you, as it seems that their documentation might have changed? I definitely used this without issue, though...there may have been a repo change as they get ready to shift, or I just recorded it here in a dumb way. |
@bradq Looks like it was indeed removed for alpha versions but planning to add it back for 5.x beta. @chopmo As beats are supposed to be available to install via official repository, i prefer to keep it that way. Adding capability to download and install from a package url is certainly possible, but it will increase the complexity. However, i am open to suggestions. |
@vkhatri I think it definitely makes sense to stick to the repos. I think my solution for now will have to be writing a custom recipe to upload a binary package and install it. Then I can go back to using this recipe once 5.x is available from the repos. Thanks for the responses, both! |
Beats docs updated. Will update cookbook shortly. https://www.elastic.co/guide/en/elasticsearch/reference/5.0/rpm.html |
working on adding 5.x support |
Added v5.x support iv v0.4.3. |
I need to push my logs to kafka and for that I might need filebeat 5.0, though it is in alpha. But I am not sure about the repo and other settings and I am relying heavy on readymade cookbooks! Is there any cook available? Help is greatly appreciated.
The text was updated successfully, but these errors were encountered: