WARNING: Version 5.6 of Beats 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.
You can use the
import_dashboards script to import all the dashboards and the index pattern for a Beat, including the dependencies such as visualizations and searches.
import_dashboards script is available under
beats/libbeat/dashboards. It’s also available in each Beat package under the
There are a couple of common use cases for importing dashboards:
- Users who are getting started with Beats may want to import dashboards and/or the index pattern for a single Beat.
- Community Beats developers may want to import dashboards for development to use as a starting point for new dashboards.
import_dashboards script from the Beat package, you can import the dashboards and the index pattern to
Elasticsearch running on localhost for a single Beat (eg. Metricbeat):
from a local directory:
./scripts/import_dashboards -dir kibana/metricbeat
from a local zip archive:
./scripts/import_dashboards -file metricbeat-dashboards-1.1.zip
from the official zip archive available at https://artifacts.elastic.co/downloads/beats/beats-dashboards/beats-dashboards-5.6.16.zip:
See Structure of the Dashboards Archive for more details about the structure of dashboard archives.
from a zip archive available online:
./scripts/import_dashboards -url https://github.com/monicasarbu/metricbeat-dashboards/archive/v1.1.zip
If you don’t specify the location of the archive, then by default it’s set to the official zip archive containing the index pattern and the dashboards of the official Beats.
To import only the index-pattern for a single Beat (eg. Metricbeat) use:
To import only the dashboards together with visualizations and searches for a single Beat (eg. Metricbeat) use:
When running the
import_dashboards script from within the Beat package, the
-beat option is set automatically to the Beat
See Command Line Options for a description of other import options.
For development or community Beats, it’s easier to run the
import_dashboards script from the beats/libbeat/dashboards directory. In this case, you need to first compile the script:
cd beats/libbeat/dashboards make
And then you can import the index pattern and the dashboards together with visualizations and searches for a single
Beat, by passing the
For example, to import the Metricbeat dashboards together with visualizations, searches, and the Metricbeat index pattern:
beats/libbeat/dashboards/import_dashboards -beat metricbeat
For this example, you must specify
-beat metricbeat. If the
-beat option is not
specified, the script imports the dashboards of all Beats.
You can make use of the Makefile from the Beat GitHub repository to import the dashboards. If Elasticsearch is running on localhost, then you can run the following command from the Beat repository:
If Elasticsearch is running on a different host, then you can use the
ES_URL="http://192.168.3.206:9200" make import-dashboards
import_dashboards script accepts the following command-line options. To see all the available options, read the descriptions below or run:
The Beat name. The Beat name is required when importing from a zip archive. When using
import_dashboardsfrom the Beat package, this option is set automatically with the name of the Beat. When running the script from source, the default value is "", so you need to set this option in order to install the index pattern and the dashboards for a single Beat. Otherwise the script imports the index pattern and the dashboards for all Beats.
- The Certificate Authority to use for server verification.
- The certificate to use for SSL client authentication. The certificate must be in PEM format.
- Local directory that contains the subdirectories: dashboard, visualization, search, and index-pattern. The default value is the current directory.
- The Elasticsearch URL. The default value is http://localhost:9200.
- Local zip archive with the dashboards. The archive can contain Kibana dashboards for a single Beat or for multiple Beats.
You should only use this option if you want to change the index pattern name that’s used by default. For example, if the
metricbeat-*, you can change it to
- If specified, "insecure" SSL connections are allowed.
The Elasticsearch index pattern where Kibana saves its configuration. The default value is
- The client certificate key. The key must be in PEM format.
- If specified, then only the dashboards, along with their visualizations and searches, are imported. The index pattern is not imported. By default, this is false.
- If specified, then only the index pattern is imported. The dashboards, along with their visualizations and searches, are not imported. By default, this is false.
- The password for authenticating the connection to Elasticsearch by using Basic Authentication. By default no username and password are used.
-snapshotwill import the snapshot dashboards build for the current version. This is mainly useful when running a snapshot Beat build for testing purpose.
-urlwill be ignored.
- Zip archive with the dashboards, available online. The archive can contain Kibana dashboards for a single Beat or for multiple Beats.
- The username for authenticating the connection to Elasticsearch by using Basic Authentication. By default no username and password are used.
The zip archive contains dashboards for at least one Beat. The index pattern, dashboards, visualizations and searches are available in a separate directory for each Beat, having the name of the Beat. For example the official zip archive (beats-dashboards-5.6.16) has the following structure:
metricbeat/ dashboard/ search/ visualization/ index-pattern/ packetbeat/ dashboard/ search/ visualization/ index-pattern/ filebeat/ index-pattern/ winlogbeat/ dashboard/ search/ visualization/ index-pattern/