IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Metricbeat and systemd Stop Metricbeat »

› ›

Start Metricbeat

edit

Start Metricbeat

edit

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.yml is authorized to publish events.

To start Metricbeat, run:

sudo service metricbeat start

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

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 
sudo chown root modules.d/{modulename}.yml 
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.d directory, or run Metricbeat with --strict.perms=false specified. See Config File Ownership and Permissions.

sudo chown root metricbeat.yml 
sudo chown root modules.d/{modulename}.yml 
sudo ./metricbeat -e

PS C:\Program Files\metricbeat> Start-Service metricbeat

By default, Windows log files are stored in C:\ProgramData\metricbeat\Logs.

On Windows, statistics about system load and swap usage are currently not captured

« Metricbeat and systemd Stop Metricbeat »