This functionality is in beta and is subject to change. The design and code is considered to be less mature than official GA features. Elastic will take a best effort approach to fix any issues, but beta features are not subject to the support SLA of official GA features.

The dashboards section of the filebeat.yml config file contains options
for automatically loading the sample Beats dashboards. Automatic dashboard
loading is disabled by default, but can be enabled either from the configuration
file or by using the -setup CLI flag.

If dashboard loading is enabled, Filebeat attempts to configure Kibana by
writing directly in the Elasticsearch index for the Kibana configuration (by
default, .kibana). To connect to Elasticsearch, Filebeat uses the
settings defined in the Elasticsearch output. If the Elasticsearch output is
not configured or not enabled, Filebeat will stop with an error. Dashboard
loading is only attempted at Beat startup. If Elasticsearch is not available when
the Beat starts, Filebeat will stop with an error.

The URL to use for downloading the dashboard archive. By default this URL
is computed based on the Beat name and version. For released versions,
this URL points to the dashboard archive on the artifacts.elastic.co
website.

In case the archive contains the dashboards for multiple Beats, this setting
lets you select the Beat for which you want to load dashboards. To load all the
dashboards in the archive, set this option to an empty string. The default is
"filebeat".