You should install Metricbeat as close as possible to the service you want to monitor. For example, if you have four servers with MySQL running, it’s recommended that you run Metricbeat on each service. This allows Metricbeat to access your service from localhost and does not cause any additional network traffic or prevent Metricbeat from collecting metrics when there are network problems. Metrics from multiple Metricbeat instances will be combined on the Elasticsearch server.
curl -L -O https://artifacts.elastic.co/downloads/beats/metricbeat/metricbeat-5.3.3-amd64.deb sudo dpkg -i metricbeat-5.3.3-amd64.deb
curl -L -O https://artifacts.elastic.co/downloads/beats/metricbeat/metricbeat-5.3.3-x86_64.rpm sudo rpm -vi metricbeat-5.3.3-x86_64.rpm
curl -L -O https://artifacts.elastic.co/downloads/beats/metricbeat/metricbeat-5.3.3-darwin-x86_64.tar.gz tar xzvf metricbeat-5.3.3-darwin-x86_64.tar.gz
- Download the Metricbeat Windows zip file from the downloads page.
Extract the contents of the zip file into
- Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator). If you are running Windows XP, you may need to download and install PowerShell.
Run the following commands to install Metricbeat as a Windows service:
PS > cd 'C:\Program Files\Metricbeat' PS C:\Program Files\Metricbeat> .\install-service-metricbeat.ps1
If script execution is disabled on your system, you need to set the
execution policy for the current session to allow the script to run. For
PowerShell.exe -ExecutionPolicy UnRestricted -File
Before starting Metricbeat, you should look at the configuration options in the
configuration file, for example
For more information about these options, see
Configuration Options (Reference).