Beats 6.0.0-beta2 released | Elastic Blog
Releases

Beats 6.0.0-beta2 released

Today we are excited to announce the Beats 6.0.0-beta2 release. As we are getting closer to the GA of 6.0, this release is primarily about bug fixes, but there are also a few new features.

Before going through the highlights, let’s get those handy links out of the way:

More consistency in Beats dashboards

As more and more dashboards are shipped with each Beat, it becomes challenging to identify which dashboard or visualization comes from which module. So, in the Beta2 release, we renamed the dashboards, searches, and visualisations of Filebeat and Metricbeat to follow a set of common naming guidelines: the dashboards start with [<Beat name> <module name>], and the visualizations and searches end with the same identifier. We plan to extend this naming practice across all dashboards created by Elastic products.

Configurable index name in dashboards

The dashboards that are shipped with each Beat are correlated with the name of the index, where the Beat’s data is stored in Elasticsearch. In case you are you using a different index than the default beatname-*, then you would need to adjust the dashboards before using them. Starting with the Beta2 release, this step is much easier as you can configure the index name when loading the Beats dashboards.

./metricbeat setup -E setup.dashboards.index=testbeat-* -e


where testbeat-* is the index name where Metricbeat is storing its data.

• #5059 The --setup flag is not working, but the setup command works.