Metricbeat Developer FAQ
The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Stack
Generally available
This is a list of common questions when creating a metricset and the potential answers.
You 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.
The 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.