I've created my own custom module to run in Metricbeat. My process locally (following this guide) was:
- clone GitHub - elastic/beats: Beats - Lightweight shippers for Elasticsearch & Logstash
- write the code in the metricset
- update the
metricbeat.ymland run the metricbeat binary
This works locally, but in a production environment what is the best practice for deploying these? Right now, we're just using system packages to handle
metricbeat but is there a simple way to add a new beat to the precompiled binaries? We could compile
metricbeat (using the steps above) each time we redeploy, but that would be a lot of time wasted compiling.
I guess I could create my own binary and use that, but that would mean actively recompiling the binary when new versions of metricbeat are released.
Is there any solid way to handle this, or is using my own binaries the best option?