Metricbeat Configuration

Ship Metrics with Metricbeat to Logstash

Metricbeat is an open-source shipping agent used to collect and ship operating system and service metrics to one or more destinations, including Logstash.

Step 1 - Install Metricbeat

deb (Debian/Ubuntu/Mint)

curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-amd64.deb
sudo dpkg -i -oss-7.15.1-amd64.deb

rpm (CentOS/RHEL/Fedora)

curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-x86_64.rpm
sudo rpm -vi -oss-7.15.1-x86_64.rpm

macOS

curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-darwin-x86_64.tar.gz
tar xzvf -oss-7.15.1-darwin-x86_64.tar.gz

Windows

Download and extract the Windows zip file.
Rename the -<version>-windows directory to ``.
Open a PowerShell prompt as an Administrator.
Run the following to install as a Windows service:

.\install-service-.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 example: PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-.ps1.

My OS isn't here! Chat to support now

Step 2 - Copy Configuration file

The configuration file below is pre-configured to send data to your Logit.io Stack via Logstash.

Copy the configuration file below and overwrite the contents of metricbeat.yml.

###################### Metricbeat Configuration Example #######################
# =========================== Modules configuration ============================

metricbeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s
# ======================= Elasticsearch template setting =======================
setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression
  #_source.enabled: false

# ================================== Outputs ===================================
# ------------------------------ Logstash Output -------------------------------
<div class="sw-warning">
    <b>No input available! </b> Your stack is missing the required input for this data source <a href="#" onclick="Intercom('showNewMessage')" class="btn btn-info btn-sm">Talk to support to add the input</a>
</div>

Step 3 - Start metricbeat

Ok, time to start ingesting data!

deb/rpm

sudo systemctl enable metricbeat
sudo systemctl start metricbeat

mac

./metricbeat

Windows

Start-Service metricbeat

Step 4 - Configure Modules (Optional)

The system status module is enabled by default to collect metrics about your server, such as CPU usage, memory usage, network IO metrics, and process statistics.

There are a range of other modules which can be enabled for Metricbeat, please choose the module from the list below if you wish to know more.

apache, docker, golang, haproxy, http, kafka, kubernetes, mongodb, mysql, nginx, rabbitmq,

redis, centos, debian, macos, redhat, ubuntu, windows, uwsgi, postgresql, zookeeper, puppet

Step 5 - how to diagnose no data in Stack

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Step 6 - Metricbeat System dashboard

The Metricbeat System module comes with predefined Kibana dashboards. To view your dashboards for any of your Logit.io stacks, launch Kibana and choose Dashboards.

Kibana dashboard preview

Step 7 - Metricbeat Overview

Metricbeat is a lightweight metrics shipper built using the Libbeat framework. It's origins started from the now deprecated Topbeat & it is used for collecting service and system log metrics to be parsed in Logstash and used across the rest of the ELK Stack.

Metricbeat makes sending data for server monitoring simpler by aggregating system metrics from a number of popular tools including NGINX, MySQL, Apache & HAProxy. While Metricbeat can push log data directly to the Elastic Stack some users may wish to use a buffering service such as Redis or Kafka. Metricbeat does much more than simply collect metrics as it can be used to tap into a variety of systems and execute a range of enhancements to the log file before shipping the metrics to ELK

The shipper when paired with Kibana can be used to report on CPU, memory and load metrics. When used in a containerised environment with Docker it can be used as a solution for container monitoring on the Logit.io platform.

Our platform provides a complete hosted ELK solution allowing you to get the best out of Metricbeat in a single centralised platform for log and metric analysis. We believe that monitoring metrics plays a crucial role in maintaining the health & security of your applications

Discover more about our Metrics-As-A-Service Solution.

If you need any further assistance with sending data through Metricbeat to Logstash we're here to help. Feel free to reach out by contacting our support team via live chat & we'll be happy to assist.

Expand View