elastic/beats

:tropical_fish: Beats - Lightweight shippers for Elasticsearch & Logstash

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 3 seconds ago
Added to GitGenius on April 7th, 2021
Created on February 5th, 2014
Open Issues & Pull Requests: 1,044 (+0)
Number of forks: 5,005
Total Stargazers: 12,640 (+0)
Total Subscribers: 653 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.4 hours
Mean response time: 103.5 days
90th percentile: 365.0 days
Tracked items: 2,171

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "ci-reported" is answered fastest, typically in under an hour, while "Stalled" waits about 5 days. 56% of tracked open issues have had no activity in three months. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 773
New in 7 days: 26
Closed in 7 days: 23
Avg open age: 393 days
Stale 30+ days: 575
Stale 90+ days: 431

Recent activity

Opened in 7 days: 17
Closed in 7 days: 19
Comments in 7 days: 85
Events in 7 days: 710

Top labels

  • needs_team (929)
  • Team:Elastic-Agent-Data-Plane (927)
  • Stalled (751)
  • bug (417)
  • enhancement (354)
  • Filebeat (242)
  • Team:Security-Service Integrations (232)
  • flaky-test (203)

Detailed Description

Beats is a collection of lightweight data shippers written in Go that form a core component of the Elastic Stack. The project provides a framework called libbeat along with seven officially supported Beat applications, each designed to collect specific types of operational data from servers and send it to Elasticsearch or Logstash for visualization and analysis in Kibana. The repository emphasizes minimal resource consumption, small installation footprints, and zero runtime dependencies as defining characteristics of the Beats architecture.

The officially supported Beats included in this repository serve distinct data collection purposes. Filebeat tails and ships log files from various sources. Metricbeat fetches metrics from operating systems and services. Packetbeat monitors networks and applications through packet sniffing. Heartbeat pings remote services to verify availability. Auditbeat collects Linux audit framework data and monitors file integrity. Winlogbeat specifically handles Windows Event logs. Osquerybeat, available in the x-pack directory, runs Osquery and manages its interactions. Beyond these official implementations, the project acknowledges a community ecosystem of additional Beats built on the libbeat framework that exist outside this repository.

The repository demonstrates substantial organizational activity and engagement.

The project's scope extends across multiple infrastructure and observability domains. This broad classification reflects the diverse use cases enabled by the various Beat implementations and their flexibility in different deployment scenarios.

The repository maintains connections with other significant Elastic projects. The project provides comprehensive documentation on the elastic.co site for each Beat implementation and the libbeat platform itself, along with getting started guides. The repository includes contribution guidelines in a CONTRIBUTING file and special instructions for AI coding agents in an AGENTS.md file. Pre-compiled binaries and packages for supported platforms are available through Elastic's downloads page, and snapshot builds generated from the main branch are provided for testing purposes. The project uses Buildkite for CI/CD pipelines with support for PR-triggered jobs and label-based build configuration for affiliated Elastic users.