Start Metricbeat [metricbeat-starting]

Before starting Metricbeat:

• Follow the steps in Quick start: installation and configuration to install, configure, and set up the Metricbeat environment.
• Make sure {{kib}} and {{es}} are running.
• Make sure the user specified in metricbeat.yml is authorized to publish events.

To start Metricbeat, run:

:::::::{tab-set}

::::::{tab-item} DEB

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. ::::::

::::::{tab-item} RPM

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. ::::::

::::::{tab-item} MacOS

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

1. 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. ::::::

::::::{tab-item} Linux

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

1. 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. ::::::

::::::{tab-item} Windows

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

By default Windows log files are stored in C:\Program Files\Metricbeat-Data\logs.

:::{note} In versions before 9.0.6, the default location for Windows log files was C:\ProgramData\metricbeat\logs. :::

::::{note} On Windows, statistics about system load and swap usage are currently not captured :::: ::::::

:::::::