WARNING: Version 5.2 of Metricbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Metricbeat Developer Guide FAQ
editMetricbeat Developer Guide FAQ
editThis is a list of common questions when creating a metricset and the potential answers.
Metricset is not compiled
editYou are compiling your Beat, but the newly created metricset is not compiled?
Make sure that the path to your module and metricset are added as an import path either in your main.go
file or your include/list.go file. You can do this manually or by running make imports.
Metricset is not started
editThe metricset is compiled, but not started when starting Metricbeat?
After creating your metricset, make sure you run make collect. This command adds the configuration
of your metricset to the default configuration. If the metricset still doesn’t start, check your
default configuration file to see if the metricset is listed there.