fluentd.org valid

Fluentd

Fluentd is an open source data collector for a unified logging layer. It decouples data sources from backend systems, so you can unify the collection and consumption of your data. Fluentd is a graduated project of the Cloud Native Computing Foundation (CNCF), and all components are available under the Apache 2 License.

For agents: Fluentd: open source data collector for unified logging, a CNCF graduated project under Apache 2.0. Offers architecture docs, quickstarts, package downloads and

log collectionunified loggingopen sourcecncflog forwarding

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T14:35:28.133Z. Cached copy · Source on fluentd.org

# Fluentd

> Fluentd is an open source data collector for a unified logging layer. It decouples data sources from backend systems, so you can unify the collection and consumption of your data. Fluentd is a graduated project of the Cloud Native Computing Foundation (CNCF), and all components are available under the Apache 2 License.

This site is the home of the Fluentd project. It explains what Fluentd is, where to download it, which plugins are available, and how to take part in the community. The reference manual lives on a separate site, https://docs.fluentd.org.

## Getting started

- [What is Fluentd?](https://www.fluentd.org/architecture): Overview of the unified logging layer and how Fluentd works.
- [Why use Fluentd?](https://www.fluentd.org/why): Reasons to choose Fluentd, such as its simple design, small footprint and plugin ecosystem.
- [Download](https://www.fluentd.org/download): Install packages and installation guides for each platform.
- [Download Fluent Package](https://www.fluentd.org/download/fluent_package): The stable distribution of Fluentd maintained by the project.
- [Documentation](https://docs.fluentd.org/llms.txt): Index of the reference manual (configuration, plugins and internals). Each page is also available as Markdown by appending `.md` to its URL.
- [FAQs](https://www.fluentd.org/faqs): Answers to common questions about Fluentd.

## Plugins and data

- [List of Data Sources](https://www.fluentd.org/datasources): Input plugins grouped by the system that produces the data.
- [List of Data Outputs](https://www.fluentd.org/dataoutputs): Output plugins grouped by the system that stores the data.
- [List of Plugins By Category](https://www.fluentd.org/plugins): List of categorized plugins published on RubyGems.
- [List of All Plugins](https://www.fluentd.org/plugins/all): Flat list of every plugin, grouped by input/output/filter/parser/formatter.

## Guides and recipes

- [Guides, Solutions and Examples](https://www.fluentd.org/guides): Index of the recipes below.
- [Adding Hostname to Event Logs (Apache httpd Example)](https://www.fluentd.org/guides/recipes/apache-add-hostname): Step by step configuration example.
- [Docker Logging](https://www.fluentd.org/guides/recipes/docker-logging): Step by step configuration example.
- [Collecting Logs into Elasticsearch and S3](https://www.fluentd.org/guides/recipes/elasticsearch-and-s3): Step by step configuration example.
- [Monitoring HAProxy Real-time with Elasticsearch and Fluentd](https://www.fluentd.org/guides/recipes/haproxy-elasticsearch): Step by step configuration example.
- [Parse Postfix Maillogs and Store Them in MongoDB](https://www.fluentd.org/guides/recipes/maillog-mongodb): Step by step configuration example.
- [Aggregating Rsyslogd Output into a Central Fluentd](https://www.fluentd.org/guides/recipes/rsyslogd-aggregation): Step by step configuration example.

## Use cases

- [Centralized Application Logging](https://www.fluentd.org/centralized_application_logg
…

Related sites

Other listed sites in DevOps and observability. See the whole category →

Machine-readable: GET /v1/resolve?q=fluentd.org · GET /v1/domain/fluentd.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fluentd.org:
1. POST https://agentwebmap.com/v1/sites/fluentd.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://fluentd.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/fluentd.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fluentd.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.