Start TrialStart Free TrialStart Free TrialBook Your DemoSign In

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 your Stack via Logstash.

Send Your DataLogsShippersMetricbeat Configuration Guide

Follow this step by step guide to get 'logs' from your system to

Step 1 - Install Metricbeat

To get started first follow the steps below:

  • Install
  • Root access
  • Verify the required port is open

Older versions can be found here 7, 6, 5

Step 2 - Copy Configuration file

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

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

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

  # 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 =======================
  index.number_of_shards: 1
  index.codec: best_compression
  #_source.enabled: false

# ================================== Outputs ===================================
# ------------------------------ Logstash Output -------------------------------
<div class="sw-warning">
        <img src="/images/source-wizard/warning-triangle.svg">
       <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>

Step 3 - Validate configuration

If you have issues starting in the next step, you can use these commands below to troubleshoot.

Let's check the configuration file is syntactically correct by running directly inside the terminal. If the file is invalid, will print an error loading config file error message with details on how to correct the problem.


sudo  -e -c /etc//.yml


sudo ./ -e -c .yml


.\.exe -e -c .yml

Step 4 - Start metricbeat

Start or restart to apply the configuration changes.

Step 5 - Check for your logs

Now you should view your data:

Launch Dashboard

If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.

Step 6 - 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 7 - 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 8 - Metricbeat System dashboard

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

Kibana dashboard preview

Step 9 - 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 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.

Return to Search
Sign Up

© 2023 Ltd, All rights reserved.