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!
University of Manitoba