@biswajit86 I'm glad you found the docs or figured it out yourself. It is definitively not 100% obvious that you have to search for these docs on CONTRIBUTING.md, but no sure what a better place would be.
There should atleast be a one-liner/hyperlink in READEMe.md that points to "how to build from source ". Its not always intuitive to get "build from source" instructions form contributing.md.
Also if you follow the steps for make command, you only get the topbeat binary. It does not generate the correspoding config files . If there are extra params/switches in the config file, it will be unobvious to the user. The make command should be modified (IMO) to generate the corresponding config file.
The topbeat yml can be taken from master. My point was that instead of end users trying to figure out where to pick individual files from, a target directory created as an output of make command can automatically add the usual files found in a package, which for now are the topbeat binary, the config file and the json template
I see. We have very similar functionality in our beats-packer that also generates the packages itself, but not based on the standard make command: https://github.com/elastic/beats/tree/master/dev-tools/packer An other solution would be to improve the docs on where to find the files (in case the docs are read ). Thanks for the inputs.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.