Beats platform的参考

2016 年 4 月 8 日2,0400





Release notes
Beats version 1.2.1
Beats version 1.2.0
Beats version 1.1.2
Beats version 1.1.1
Beats version 1.1.0
Beats version 1.0.1
Beats version 1.0.0
Beats version 1.0.0-rc2
Beats version 1.0.0-rc1
Beats version 1.0.0-beta4


A regular Beats setup consists of:

One or more Beats. You install the Beats on your servers to capture operational data.
Elasticsearch for storage and indexing. See Installing Elasticsearch.
Logstash (optional) for inserting data into Elasticsearch. See Installing Logstash.
Kibana for the UI. See Installing Kibana.
Kibana dashboards for visualizing the data. See Loading the Beats Dashboards.


The Beats dashboards require Kibana 4 or later.

To load the sample dashboards, you run a load script. The load script uploads the example dashboards, visualizations, and searches that you can use. The load command also creates index patterns for each Beat:

Use the following commands to run the script:

deb, rpm, and mac:

curl -L -O
cd beats-dashboards-1.2.1/
By default, the script assumes that you are running Elasticsearch on Use the -url option to specify a different location. For example: ./ -url To specify a Kibana index pattern or pass in user credentials, see Other Dashboard Load Options.


Other Dashboard Load Options

Beats Platform Reference:

When you load the Beats dashboards, you can also specify:

The Kibana index pattern where you want to load the dashboards in Elasticsearch. For example:

./ -url -index .kibana_env
The username and password to use for authentication. There are a few ways to pass in the username and password. For example:

./ -url -u user:password

./ -url -u admin:$(cat ~/pass-file)

./ -url

Specify the username and password separated by a colon.


Use a file to avoid polluting the bash history with the password.


Put the username and password in the URL.

These options are also available when you run .\load.ps1 on Windows.




Packetbeat Dashboard

0 0