beats
by
elastic

Description: :tropical_fish: Beats - Lightweight shippers for Elasticsearch & Logstash

View on GitHub ↗

Summary Information

Updated 2 hours ago
Added to GitGenius on April 7th, 2021
Created on February 5th, 2014
Open Issues & Pull Requests: 1,011 (+4)
Number of forks: 5,007
Total Stargazers: 12,635 (+1)
Total Subscribers: 654 (+0)

Issue Activity (beta)

Open issues: 727
New in 7 days: 2
Closed in 7 days: 7
Avg open age: 361 days
Stale 30+ days: 636
Stale 90+ days: 414

Recent activity

Opened in 7 days: 2
Closed in 7 days: 4
Comments in 7 days: 3
Events in 7 days: 10

Top labels

  • needs_team (857)
  • Team:Elastic-Agent-Data-Plane (851)
  • Stalled (747)
  • bug (391)
  • enhancement (336)
  • Filebeat (232)
  • Team:Security-Service Integrations (177)
  • flaky-test (173)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 11.5 days
90th percentile: 7.2 days
Tracked items: 2,347

Most active contributors

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. GitGenius tracking shows 2347 issues and pull requests with a median response latency of zero hours and a mean response time of 275.4 hours, indicating active triage and handling of submissions. The most frequently applied issue labels reveal organizational structure, with Team:Elastic-Agent-Data-Plane accounting for 851 tracked events, Stalled for 609 events, and needs_team for 490 events. The most active contributors tracked include elasticmachine with 1767 events, belimawr with 856 events, and cmacknz with 604 events, showing concentrated maintenance activity among key team members.

The project's scope extends across multiple infrastructure and observability domains. GitGenius classification identifies the repository as relevant to cloud infrastructure, log collection, performance tracking, event data, logging, system metrics, observability, data collection, security analytics, system logs, application monitoring, network monitoring, network traffic, Logstash integration, data shipping, Kubernetes, cloud integration, security auditing, and performance metrics. 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. GitGenius identifies overlapping contributors with github/gh-aw, solo-io/gloo, and elastic/kibana, indicating shared development resources and architectural alignment across the Elastic ecosystem. 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.

beats
by
elasticelastic/beats

Repository Details

Fetching additional details & charts...