FAQ
Last updated
Was this helpful?
Last updated
Was this helpful?
fluentd
support?Latest fluentd works on Ruby 2.7 or later.
Though the minimum required version is Ruby 2.7 or later, we recommend using fluentd
with more newer stable version.
No difference. v1 is built on top of v0.14. Use v1 for a newer installation. We use v1 or v1.x on our document.
The timestamps of Fluentd and its logger libraries depend on your system's clock. It is highly recommended that you set up NTP on your nodes so that your clocks remain synced with the correct clocks.
td-agent
/fluent-package
and want to add custom plugins. How do I do it?Use the bundled gem system. See for more information.
You can use the copy
to send the same event to multiple output destinations.
Use "#{ENV['YOUR_ENV_VARIABLE']}"
. For example:
Note that it must be double quotes, not single quotes.
host:port
. Why?There are several reasons:
If you get Address already in use
error, another process has already
used host:port
. Check port conflict between processes/plugins.
If you get Permission denied
error, you likely tried to use a well-known
port without permission. Search well-known ports
for how to use well-known ports.
Use capabilities
or something.
If you get other errors, Google it.
tzinfo
conflict error after installed pluginsFluentd supports tzinfo v1.1 or later and recent td-agent / fluent-package / official images install tzinfo v2 by default. The problem is several plugins depend on ActiveSupport and ActiveSupport doesn't support tzinfo v2. To resolve this problem, there are 2 approaches.
Uninstall tzinfo v2 and install tzinfo v1.1 manually
Update plugin to remove ActiveSupport dependency. ActiveSupport is mainly for Ruby on Rails,
so using ActiveSupport for several convenient methods is overengineering.
Former is easier approach.
no patterns matched
in the log, why?This means that the event is emitted but there is no <match>
directive for it. For example, if you emit the event with foo.bar
tag, you need to define <match>
for foo.bar
tag like <match foo.**>
.
You may hit "\xC3" from ASCII-8BIT to UTF-8
like UndefinedConversionError
in the plugin. This error happens when string encoding is set to ASCII-8BIT
but the actual content is UTF-8
. Fluentd and all its plugins treat the logs as ASCII-8BIT
by default but some libraries assume that the log encoding is UTF-8
. This is why this error occurs.
There are several approaches to avoid this problem:
Set encoding correctly:
The tail
input plugin has encoding related parameters to change the
log encoding.
Use record_modifier
filter plugin to change the encoding. See
Use yajl
(Yajl.load
/Yajl.dump
) instead of json
when error happens
inside JSON.parse
/JSON.dump
/to_json
.
Oj is not installed, and falling back to Yajl for json parser
.If you are using Alpine Linux, you need to install ruby-bigdecimal
to use Oj
as the JSON parser. Please Execute the following command to see if the warning persists:
<my complex text log>
?See also: or
file
buffer has limitations. Check .
.
Please refer to the .
If you are willing to write Regexp, or is a great tool to verify your Regexps.
If you do NOT want to write any Regexp, look at .
If this article is incorrect or outdated, or omits critical information, please . is an open-source project under . All components are available under