FAQ
Last updated
Was this helpful?
Last updated
Was this helpful?
Fluentd v0.12 works on 1.9.3 or later. Since v1.x, 2.1 or later.
The rubygems of Ruby 2.0-p353 has a deadlock problem (). If you use Ruby 2.0-p353, upgrading Ruby to latest patch level or Ruby 2.1 resolve this problem.
Please make sure that you are using either RHEL 7.1 and ruby-2.0.0.598-25.el7_1 package or alternatively you can choose more recent Ruby provided by Red Hat Software Collections ()
Unfortunately, Ruby 2.0 package of Ubuntu 14.04 use Ruby 2.0-p353. So don't use Fluentd with Ruby 2.0 package on this environment. You can install specified Ruby version using .
Using td-agent is another way to avoid this problem because td-agent includes own Ruby.
In v0.12 or earlier, fluentd's event time is second unit. It means fluentd converts millisecond/nanosecond timestamp into second timestamp.
Since v1.x, event tims has nanosecond resolution, so fluentd can handle millisecond/nanosecond timestamp properly.
Visit
The timestamps of Fluentd and its logger libraries depend on your system's clock. It's highly recommended that you set up NTP on your nodes so that your clocks remain synced with the correct clocks.
td-agent has own Ruby so you should install gems into td-agent's Ruby, not system Ruby.
Please use td-agent-gem as shown below.
For example, issue the following command if you are adding fluent-plugin-twitter.
Now you might be wondering, "Why do I need to specify the full path?" The reason is that td-agent does not modify any host environment variable, including PATH. If you want to make all td-agent/fluentd related programs available without writing "/usr/lib/..." every time, you can add
to your ~/.bash_profile.
Use "#{ENV['YOUR_ENV_VARIABLE']}". For example,
Note that it must be double quotes and not single quotes
There are several reasons:
If you get Address already in use error, other process has already
used host:port. Check port conflict between processes / plugins.
If you get Permission denied error, you try to use well-known
port. Search well-known port for how to use well-known port. Use
capabilities or something
If you get other errors, google it.
This means you emit the event but no <match> directive for emitted event. 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 actual content is UTF-8. Fluentd and almost plugins treat the logs as a ASCII-8BIT by default but some libraries assume the log encoding is UTF-8. This is why this error happens.
There are several approaches to avoid this problem.
Set encoding correctly.
tail input has encoding related parameters to change the log
encoding
Use record_modifier filter to change the encoding. See
[fluent-plugin-record-modifier
Use yajl instead of json when error happens inside
JSON.parse/JSON.dump
<my complex text log>?If you would like to find out more about plugin management, please take a look at the article.
You installed v1.0 based plugin. See .
You can use the copy to send the same event to multiple output destinations.
See also: or
file buffer has limitations. Check .
README]()
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 a open source project under . All components are available under the Apache 2 License.