# Unable to Create new Beat based on Metricbeat

**URL:** <https://discuss.elastic.co/t/unable-to-create-new-beat-based-on-metricbeat/163552>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [January 9, 2019, 2:41pm UTC](https://discuss.elastic.co/t/unable-to-create-new-beat-based-on-metricbeat/163552 "2019-01-09T14:41:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eifoen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eifoen/32/39652_2.png) [@Eifoen](https://discuss.elastic.co/u/Eifoen)\
**Post date:** [January 9, 2019, 2:41pm UTC](https://discuss.elastic.co/t/unable-to-create-new-beat-based-on-metricbeat/163552/1 "2019-01-09T14:41:24Z")

</div>

Hi Folks,

I spend the last 2 days trying to get up and running with my own Beat.

I ended up literally installing a dedicated Ubntu 18.04 VM with:

- python2 (because the build script uses 'python' instead of 'python2' _argh_)
- virtenv (because the build script uses 'virtenv' instead of 'virtenv2' _argh aswell_)
- go + utils
- wget
- git
- atom with go-plus

I followed the Instructions here: [https://www.elastic.co/guide/en/beats/devguide/current/creating-beat-from-metricbeat.html](https://www.elastic.co/guide/en/beats/devguide/current/creating-beat-from-metricbeat.html)

(of course I read the complete chapter about building beats)

Problems encountered so far:

- make setup only works when issued twice - first try fails with "make: \*\*\* no rule for create-metricset"  
(but hey.. second try solves it..) (might be a symlink problem)

- when beats repo is checked out at current master (commit 4a228013c933de154c4e21a296c61ec44ac38530), like the instructions tell me too, executing "make" returns afeter approximately 1 sec doing nothing at all. (works when I checkout 6.5 though)

- Executing "make collect" does not work at all (6.5 / master). It return with "grep: ../libbeat/docs/version.asciidoc: file or directory not found"  
This is perfectly normal because this only exists relative to the metricbeat repo and from my beats location is located under "./vendor/....". =\> Bug in build-scripts?  
Finally (when I create a symlink to $GOPATH/src/github.com/elastic/beats/libbeat at ../libbeat) the grep for the version.ascii works fine but make collect return with "cp: stat for 'module/\*/\_meta/kibana/\*' not possible: file or directory not found  
vendor/github.com/elastic/beats/metricbeat/Makefile:19: recipe for target 'kibana' failed"

After all of this I really got the feeling that the build scripts of the beats templating are, at best, messed up. 😭

Does anyone have a workaround for these problems, or am I just to dump to use the templating system? 😕

BTW: This was all tested without altering any file within.

Greetings, Eifoen

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 6, 2019, 4:41pm UTC](https://discuss.elastic.co/t/unable-to-create-new-beat-based-on-metricbeat/163552/2 "2019-02-06T16:41:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.