WARNING: Version 5.2 of Metricbeat 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.
Step 4: Starting Metricbeatedit
Run Metricbeat by issuing the appropriate command for your platform.
If you use an init.d script to start Metricbeat on deb or rpm, you can’t specify command line flags (see Command Line Options). To specify flags, start Metricbeat in the foreground.
deb:
sudo /etc/init.d/metricbeat start
rpm:
sudo /etc/init.d/metricbeat start
mac:
sudo ./metricbeat -e -c metricbeat.yml -d "publish"
win:
PS C:\Program Files\Metricbeat> Start-Service metricbeat
By default the log files are stored in C:\ProgramData\metricbeat\Logs.
On Windows, statistics about system load and swap usage are currently not captured.
Testing the Metricbeat Installationedit
To verify that your server’s statistics are present in Elasticsearch, issue the following command:
curl -XGET 'http://localhost:9200/metricbeat-*/_search?pretty'
Make sure that you replace localhost:9200 with the address of your
Elasticsearch instance.
On Windows, if you don’t have cURL installed, simply point your browser to the URL.