If you are adding a module, please consider adding it to upstream elastic/beats at metricbeat.
If you prefer to get your way your on the right path.
Can you take a look at the cmd/root.go file and check the contents of variable Name at that file? iirc the name of the metricbeat default config is taking from there.
Not sure if the generator you've used should've created a sample yaml config file, but you can copy the one you use at metricbeat stripping all non used parameters.
If you are extending metricbeat you will be either adding a new set of metrics (metricset) to an existing module, or creating a new module if the system you want to monitor doesn't already exists here:
Either case, you fork the repo, and probably the first thing to do is building the binary without any modification to make sure your environment is set.
Can you try to compile and run metricbeat without modifying anything yet?
If I'm understanding correctly you don't want a new beat, but extend current metricbeat functionality, in such case /mybeat shouldn't exist.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.