# Custom beat module ready, how to install?

**URL:** <https://discuss.elastic.co/t/custom-beat-module-ready-how-to-install/155601>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [November 6, 2018, 7:05pm UTC](https://discuss.elastic.co/t/custom-beat-module-ready-how-to-install/155601 "2018-11-06T19:05:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sentient](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sentient/32/34996_2.png) [@sentient](https://discuss.elastic.co/u/sentient)\
**Post date:** [November 6, 2018, 7:05pm UTC](https://discuss.elastic.co/t/custom-beat-module-ready-how-to-install/155601/1 "2018-11-06T19:05:50Z")

</div>

I got myself through some hiccups, but I finally got the 'make package' working. Now a few questions

- I can build _with_ or _without_ snapshot. Not sure what the difference is
- I can install my custom package `sudo dpkg -i udpproto-6.3.3-SNAPSHOT-amd64.deb` but that installs it under \etc\udpproto. Does every module need a new folder? Is it possible I can deploy this to the installed metricbeat\modules.d folder?
- I also noticed it has it's own service. But ideally I just want to use the metricbeat service.
- I could not find much documentation on how to install a custom module and what are the best practices. I keep on getting back to the standard shipped modules that comes with metricbeat.

I'm sure these are just a lot of newbie questions for a first time module creator. The code generation and examples got me pretty far. Just have to get over that last part on deploying and installation...

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [November 12, 2018, 12:40pm UTC](https://discuss.elastic.co/t/custom-beat-module-ready-how-to-install/155601/2 "2018-11-12T12:40:33Z")

</div>

Hi @sentient,

How did you create your beat module? If you did it with the instructions to create a new beat, then actually you have created a new complete beat. Even if it is based in the same code as other beats, it will have its own files and configuration paths, and it will be run as a separated service.

If you created it [based on metricbeat](https://www.elastic.co/guide/en/beats/devguide/6.4/creating-beat-from-metricbeat.html), then it should be easy to move the module files to metricbeat. For that you can also follow the instructions to create a [new metricbeat module](https://www.elastic.co/guide/en/beats/devguide/6.4/creating-metricbeat-module.html) and migrate the code you already have. If you do that you can run your module as part of metricbeat.

If you create a new module or metricset we'd be happy to review and include it in upstream metricbeat 🙂

---

<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:** [December 10, 2018, 12:48pm UTC](https://discuss.elastic.co/t/custom-beat-module-ready-how-to-install/155601/3 "2018-12-10T12:48:14Z")

</div>

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