fluent/fluentd

Fluentd: Unified Logging Layer (project under CNCF)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 4th, 2026
Created on June 19th, 2011
Open Issues & Pull Requests: 134 (+0)
GitHub issues: Enabled
Number of forks: 1,406
Total Stargazers: 13,581 (+0)
Total Subscribers: 328 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.4 hours
Mean response time: 84.4 days
90th percentile: 179.0 days
Tracked items: 173

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "CI" is answered fastest, typically in under an hour, while "enhancement" waits about 3 days. Only 4% of issues opened in the past year have been closed. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 36
New in 7 days: 1
Closed in 7 days: 2
Avg open age: 827 days
Stale 30+ days: 31
Stale 90+ days: 28

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (41)
  • bug (37)
  • waiting-for-user (28)
  • CI (24)
  • stale (24)
  • memory (9)
  • Non fluentd issue (8)
  • work-in-progress (7)

Detailed Description

Fluentd is a log collector that gathers events from various data sources and writes them to files, databases, cloud services, and other destinations.

Fluentd solves the problem of fragmented logging infrastructure by providing a unified layer that collects events from diverse sources and routes them to multiple outputs. The tool uses a plugin-based architecture that allows it to connect to numerous input sources and output destinations, enabling organizations to standardize how logs are collected and processed across their systems.

Teams should adopt Fluentd when they need to consolidate logs from multiple applications and infrastructure components into centralized storage or analysis systems. It suits projects ranging from small deployments to large-scale distributed systems, particularly those already using or considering cloud-native technologies. The tool is especially valuable for organizations seeking to avoid vendor lock-in by maintaining flexibility in where logs are stored and processed.

The project maintains active development on the master branch for the current version, with a deprecated earlier branch no longer receiving support. Development requires Ruby and git, with a standard test suite run through bundler and rake. The project maintains a security-conscious posture, having commissioned a third-party security audit and providing a dedicated security contact process for vulnerability reports.