WARNING: Version 1.1 of Beats has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Community Beats
editCommunity Beats
editThe open source community has been hard at work developing new Beats. You can check out some of them here:
|
Reads status from Apache HTTPD server-status. |
|
|
Reads docker container statistics and indexes them in Elasticsearch. |
|
|
Reads status from an Elasticsearch cluster and indexes them in Elasticsearch. |
|
|
Periodically executes shell commands and sends the standard output and standard error to Logstash or Elasticsearch. |
|
|
Collects facts from Facter. |
|
|
Collects, parses and indexes sflow samples. |
|
|
Reads all performance counters in Java HotSpot VM. |
|
|
Polls multiple HTTP(S) endpoints and sends the data to Logstash or Elasticsearch. Supports all HTTP methods and proxies. |
|
|
For Nagios checks and performance data. |
|
|
Reads status from Nginx. |
|
|
Reads status from PHP-FPM. |
|
|
Sends ICMP pings to a list of targets and stores the round trip time (RTT) in Elasticsearch. |
|
|
Used for Redis monitoring. |
|
|
Reads tweets for specified screennames. |
|
|
Reads records from Unified2 binary files generated by network intrusion detection software and indexes the records in Elasticsearch. |
|
|
Reads stats from uWSGI. |
|
|
Ships structured logs via UDP. |
Have you created a Beat that’s not listed? If so, add the name and description of your Beat to the source document for Community Beats and open a pull request in GitHub to get your change merged.
Elastic provides no warranty or support for community-sourced Beats.
Contributing to Beats
editRemember, you can be a Beats developer, too. Learn how