# Metricset creation is broken on forked beats tree?

**URL:** <https://discuss.elastic.co/t/metricset-creation-is-broken-on-forked-beats-tree/167326>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 6, 2019, 4:07pm UTC](https://discuss.elastic.co/t/metricset-creation-is-broken-on-forked-beats-tree/167326 "2019-02-06T16:07:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Grigory\_Shamov](https://avatars.discourse-cdn.com/v4/letter/g/ec9cab/32.png) [@Grigory\_Shamov](https://discuss.elastic.co/u/Grigory_Shamov)\
**Post date:** [February 6, 2019, 4:07pm UTC](https://discuss.elastic.co/t/metricset-creation-is-broken-on-forked-beats-tree/167326/1 "2019-02-06T16:07:32Z")

</div>

HI,

Is it possible to develop metricset on a forked elastic/beats repository?  
Right now it seems that the build system is broken. When forking the repo, and then doing make create-metricset, the boilerplate code gets created. However, make collect; make builds a disfunctional metricbeat that gives the following error when ran:

2019-02-05T11:42:26.495-0800 INFO instance/beat.go:410 metricbeat stopped.  
2019-02-05T11:42:26.496-0800 ERROR instance/beat.go:800 Exiting: 1 error: 1 error: metricset 'infiniband/counters' is not registered, module not found  
Exiting: 1 error: 1 error: metricset 'infiniband/counters' is not registered, module not found

Doing exactly same step from cloned (not forked) elastic/beats works (a boilerplate metricset with single counter register)

I consider it a bug. Is it not? Should build system be robust enough to survive forking? Should an issue be opened on elastic github for it? Thanks!

Grigory Shamov  
University of Manitoba

---

<div class="post-metadata">

**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\
**Post date:** [February 7, 2019, 10:37am UTC](https://discuss.elastic.co/t/metricset-creation-is-broken-on-forked-beats-tree/167326/2 "2019-02-07T10:37:22Z")

</div>

Hi @Grigory_Shamov

No, it's not possible, but it's pretty simple. You just download only the original `elastic/beats`. You work on `elastic/beats` folder and push changes to new branches in your fork (which you don't need to download).

This is the preferred way we have to work in Beats and it's by design. 🙂

Thanks for you comments!

---

<div class="post-metadata">

**Author:** ![Grigory\_Shamov](https://avatars.discourse-cdn.com/v4/letter/g/ec9cab/32.png) [@Grigory\_Shamov](https://discuss.elastic.co/u/Grigory_Shamov)\
**Post date:** [February 7, 2019, 7:23pm UTC](https://discuss.elastic.co/t/metricset-creation-is-broken-on-forked-beats-tree/167326/3 "2019-02-07T19:23:23Z")

</div>

Thanks!

---

<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:** [March 7, 2019, 7:23pm UTC](https://discuss.elastic.co/t/metricset-creation-is-broken-on-forked-beats-tree/167326/4 "2019-03-07T19:23:26Z")

</div>

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