🐠 Beats - Lightweight shippers for Elasticsearch & Logstash
Go Python Shell Makefile ApacheConf Thrift Other
Latest commit fc5ee58 Jan 18, 2017 @ruflin ruflin committed with tsg Adjust default period to 10s in generator (#3377)
Update data.json to also have dynamic values.
Failed to load latest commit information.
.github Update Github issue template with address for reporting security vuln… Nov 17, 2016
dev-tools Cleanup before_build script (#3386) Jan 17, 2017
filebeat Fix flaky metricbeat test (#3391) Jan 17, 2017
generate Refactor docs related to GOPATH (#3392) Jan 17, 2017
heartbeat Add heartbeat 'beta' log message (#3367) Jan 16, 2017
libbeat Add fetching of testify to prepare-tests (#3393) Jan 17, 2017
metricbeat Adjust default period to 10s in generator (#3377) Jan 18, 2017
packetbeat Refactor docs related to GOPATH (#3392) Jan 17, 2017
scripts Update dependencies (#1905) Jun 24, 2016
testing/environments Expose Logstash REST API in testing environment (#3316) Jan 10, 2017
vendor Add environment variables to the system process metricset (#3337) Jan 12, 2017
winlogbeat Use 0600 for files created by Beats (#3387) Jan 17, 2017
.appveyor.yml Update Go to version 1.7.4 (#3277) Jan 3, 2017
.editorconfig Fix typo in crawler Feb 24, 2016
.gitattributes Add missing gitattributes for CHANGELOG.asciidoc Jan 7, 2016
.gitignore Filebeat modules: first step of Go implementation (#3333) Jan 16, 2017
.travis.yml Update Go to version 1.7.4 (#3277) Jan 3, 2017
CHANGELOG.asciidoc Use 0600 for files created by Beats (#3387) Jan 17, 2017
CONTRIBUTING.md Refactor docs related to GOPATH (#3392) Jan 17, 2017
Dockerfile Update Go to version 1.7.4 (#3277) Jan 3, 2017
LICENSE Initial commit for beat-generator Jan 22, 2016
Makefile Set config file mode to 0600 in packages (#3382) Jan 17, 2017
NOTICE Add NOTICE file for Beats (#3334) Jan 16, 2017
README.md Updated the main README file (#2801) Oct 21, 2016
Vagrantfile Update vagrant boxes to Go 1.7.3 (#2927) Nov 3, 2016
codecov.yml Add codecov.yml file to disable comments (#1522) Apr 28, 2016
glide.yaml Set config file mode to 0600 in packages (#3382) Jan 17, 2017


Travis AppVeyor GoReportCard codecov.io

Beats - The Lightweight Shippers of the Elastic Stack

The Beats are lightweight data shippers, written in Go, that you install on your servers to capture all sorts of operational data (think of logs, metrics, or network packet data). The Beats send the operational data to Elasticsearch, either directly or via Logstash, so it can be visualized with Kibana.

By "lightweight", we mean that Beats have a small installation footprint, use limited system resources, and have no runtime dependencies.

This repository contains libbeat, our Go framework for creating Beats, and all the officially supported Beats:

Beat Description
Filebeat Tails and ships log files
Metricbeat Fetches sets of metrics from the operating system and services
Packetbeat Monitors the network and applications by sniffing packets
Winlogbeat Fetches and ships Windows Event logs

In addition to the above Beats, which are officially supported by Elastic, the community has created a set of other Beats that make use of libbeat but live outside of this Github repository. We maintain a list of community Beats here.

Documentation and Getting Started

You can find the documentation and getting started guides for each of the Beats on the elastic.co site:

Getting Help

If you need help or hit an issue, please start by opening a topic on our discuss forums. Please note that we reserve GitHub tickets for confirmed bugs and enhancement requests.


You can download pre-compiled Beats binaries, as well as packages for the supported platforms, from this page.


We'd love working with you! You can help make the Beats better in many ways: report issues, help us reproduce issues, fix bugs, add functionality, or even create your own Beat.

Please start by reading our CONTRIBUTING file.

If you are creating a new Beat, you don't need to submit the code to this repository. You can simply start working in a new repository and make use of the libbeat packages, by following our developer guide. After you have a working prototype, open a pull request to add your Beat to the list of community Beats.

Building Beats from the Source

See our CONTRIBUTING file for information about setting up your dev environment to build Beats from the source.