🐠 Beats - Lightweight shippers for Elasticsearch & Logstash
Pull request Compare This branch is 2743 commits behind elastic:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.github
dev-tools
filebeat
generate
heartbeat
libbeat
metricbeat
packetbeat
scripts
testing/environments
vendor
winlogbeat
.appveyor.yml
.editorconfig
.gitattributes
.gitignore
.travis.yml
CHANGELOG.asciidoc
CONTRIBUTING.md
Dockerfile
LICENSE
Makefile
README.md
Vagrantfile
codecov.yml
glide.yaml

README.md

Travis AppVeyor GoReportCard codecov.io

Beats - Lightweight shippers for Elasticsearch & Logstash

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

This repository contains libbeat and all the officially supported Beats, in the following folders:

Folder Description
libbeat The Go framework for creating new Beats
Filebeat Lightweight log forwarder to Logstash & Elasticsearch
Heartbeat Testing service availability using PING based on ICMP, TCP or higher level protocols
Metricbeat Fetches sets of metrics from the operating system and services
Packetbeat Tap into your wire data
Winlogbeat Sends 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 Help

You can find the documentation on the elastic.co site. If you need help, you can open a topic on our discuss forums.

Contributing

We'd love working with you! You can help making 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.