Start Metricbeat
Before starting Metricbeat:
- Follow the steps in Quick start: installation and configuration to install, configure, and set up the Metricbeat environment.
- Make sure Kibana and Elasticsearch are running.
- Make sure the user specified in
metricbeat.ymlis authorized to publish events.
To start Metricbeat, run:
sudo service metricbeat start
Note
If you use an init.d script to start Metricbeat, you can’t specify command line flags (see Command reference). To specify flags, start Metricbeat in the foreground.
Also see Metricbeat and systemd.
sudo service metricbeat start
Note
If you use an init.d script to start Metricbeat, you can’t specify command line flags (see Command reference). To specify flags, start Metricbeat in the foreground.
Also see Metricbeat and systemd.
sudo chown root metricbeat.yml 1
sudo chown root modules.d/{modulename}.yml 1
sudo ./metricbeat -e
- You’ll be running Metricbeat as root, so you need to change ownership of the configuration file and any configurations enabled in the
modules.ddirectory, or run Metricbeat with--strict.perms=falsespecified. See Config File Ownership and Permissions.
sudo chown root metricbeat.yml 1
sudo chown root modules.d/{modulename}.yml 1
sudo ./metricbeat -e
- You’ll be running Metricbeat as root, so you need to change ownership of the configuration file and any configurations enabled in the
modules.ddirectory, or run Metricbeat with--strict.perms=falsespecified. See Config File Ownership and Permissions.
PS C:\Program Files\metricbeat> Start-Service metricbeat
By default, Windows log files are stored in C:\ProgramData\metricbeat\Logs.
Note
On Windows, statistics about system load and swap usage are currently not captured