/etc/fluent/plugin
directory.TYPE
prefix could be:in
out
filter
parser
formatter
storage
buf
sd
fluent-plugin-xxx-alt
is considered the last option.yajl/json_gem
from plugin. (yajl/json_gem
compatibility layer is problematic, not for yajl
itself) It breaks a functionality to parse Fluentd's configuration completely./etc/fluent/plugin/
directory), create a <TYPE>_<NAME>.rb
file in any editor/IDE of your choice.bundle gem
to create the plugin source tree and then git init
it. It requires the bundler
gem in your Ruby environment.lib
, fluent-plugin-my_awesome.gemspec
file, README.md
and other relevant files.lib
i.e.:fluent-plugin-generate
is provided to generate the project skeleton for writing a Fluentd plugin as a Gem package.http2
, the command would be:--no-license
option. For more details, see fluent-plugin-generate --help
.fluentd
with the -vv
command-line option to show debugging messages:stdout
and copy
output plugins are useful for debugging. The stdout
output plugin dumps matched events to the standard output (console). It can be configured like this:test-unit
as the unit test library. Fluentd's test drivers assume that the test code uses it. Add test-unit
as the development dependency in your gemspec
, add Rake
task to run tests in your Rakefile
and write test code in test/plugin/test_in_my_awesome.rb
.bundle
to execute tests:README.md
showing the project skeleton generated with fluent-plugin-generate
.fluent-plugin-config-format
command.fluent-plugin-config-format --help
.