You already have an exiting installation of Flume-NG but want to collect data into backend other than HDFS (for which Flume-NG is optimized).
The benefit of this approach is:
Install the Latest Flume-NG Fluentd Sink jar into ${FLUME_HOME}/lib:
FLUME_HOME $ tree -L 1 .
.
├── CHANGELOG
├── DEVNOTES
├── LICENSE
├── NOTICE
├── README
├── RELEASE-NOTES
├── bin
├── conf
├── docs
├── lib # <- Put flume-ng-fluentd-sink-LATEST_VERSION-all.jar here.
└── tools
Write Flume-NG configuration like this:
a1.sinks = k1
a1.sinks.k1.type = com.github.cosmo0920.fluentd.flume.plugins.FluentdSink
al.sinks.k1.hostname = localhost
a1.sinks.k1.port = 24224
a1.sinks.k1.tag = flume.fluentd.sink
a1.sinks.k1.format = text
Open your Fluentd configuration file and add the following lines:
<source>
type forward
bind 0.0.0.0
port 24224
</source>
That's it. Now, you can send Flume-NG events into Fluentd via flume-ng-fluentd-sink
.
It's time to configure data outputs. Here are some examples.
Want to learn the basics of Fluentd? Check out these pages.
Couldn't find enough information? Let's ask the community!
You need commercial-grade support from Fluentd committers and experts?
©2010-2025 Fluentd Project. ALL Rights Reserved.
Fluentd is a hosted project under the Cloud Native Computing Foundation (CNCF). All components are available under the Apache 2 License.