# Export template from custom beat based on metricbeat

**URL:** <https://discuss.elastic.co/t/export-template-from-custom-beat-based-on-metricbeat/119250>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [February 9, 2018, 2:03pm UTC](https://discuss.elastic.co/t/export-template-from-custom-beat-based-on-metricbeat/119250 "2018-02-09T14:03:21Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dcroonen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dcroonen/32/27450_2.png) [@dcroonen](https://discuss.elastic.co/u/dcroonen)\
**Post date:** [February 13, 2018, 8:56am UTC](https://discuss.elastic.co/t/export-template-from-custom-beat-based-on-metricbeat/119250/5 "2018-02-13T08:56:59Z")

</div>

@steffens Thanks for your insights and effort.

> [@steffens](#):
>
> Makes me wonder, how come you're using the cmd/instance package instead of having a root command?

To be honest I have no idea. I had some issues when creating a new beat based on metricbeat. After searching a bit, I found this [thread](https://discuss.elastic.co/t/step-3-init-and-create-the-metricset-failure/112046/11), which has a solution that also worked for me. Maybe this is the root cause of the problem?

Can I fix this manually or would it be better to create a new beat based on metricbeat?

---

_[View the full topic](https://discuss.elastic.co/t/export-template-from-custom-beat-based-on-metricbeat/119250)._