Fluentd Blog

Drop schedule announcement in 2019

Hi users and developers!

We announce the drop schedule for Fluentd development.

Fluentd

Fluentd now has v1 and v0.12 versions. v0.12 is old stable and v0.12 is now security maintenance mode. To focus v1 development, we will stop all activities for v0.12 in the end of 2019.

• Stop to accept security fix patches
• Stop to update docker images
• Stop to handle v0.12 issues/questions

We recommend plugin developers to use v1 API for full v1 feature support :)

Treasure Agent(td-agent)

td-agent 2.3 is no longer supported. If you want to use td-agent for fluentd v0.12, use td-agent 2.5 instead. td-agent 2.5 uses ruby 2.5, so td-agent 2.5 is more better than td-agent 2.3.

Of course, we recommend to use td-agent 3, fluentd v1 serise, for new deployment :)

Ruby

Fluentd now supports ruby 2.1 or later but it makes code harder to maintain. For better development, we will drop ruby 2.1, 2.2 and 2.3 support in the end of 2019. Supporting ruby 2.4 or later is reasonable because almost users now run fluentd on ruby 2.4 or later.

• td-agent 2.5 uses ruby 2.5
• td-agent 3 uses ruby 2.4
• td-agent 4 will use ruby 2.6
• Alpine docker images use ruby 2.5
• Debian docker images use ruby 2.6
• Latest OSes(CentOS 8, Ubuntu 18.04, Debian 10, etc) use ruby 2.4 or later

In addition, we can use rvm/rbenv to install any ruby version, so we hope dropping ruby 2.3 or earlier doesn't have big impact for existing users.

If you have any question, post it to mailing list ;)

Read More

Fluentd v1.7.4 has been released

Hi users!

We have released v1.7.4. ChangeLog is here. This release is mainly for fixing bugs.

in_http: Add use_204_response parameter

This change follows RFC7231. For zero-length payload, 204 is better than 200.

<source>
  @type http
  # other parameters
  use_204_response true
</source>

This parameter will be removed at fluentd v2 and in_http will return 204.

Major bug fixes

• child_process helper: fix stderr blocking for discard case
• log: Fix log rotation handling on Windows. This changes log filename. See https://docs.fluentd.org/deployment/logging#log-rotation-setting

Enjoy logging!

Read More

Fluentd v1.7.3 has been released

Hi users!

We have released v1.7.3. ChangeLog is here. This release is mainly for fixing socket cache bug of out_forward.

in_syslog: Replace priority_key with severity_key

in_syslog's priority_key parameter is misleading name because it sets severity, not priority value. So we add severity_key parameter.

<source>
  @type syslog
  severity_key severity
  tag syslog
</source>

priority_key is still supported for existing users but we will remove priority_key parameter at fluentd v2.

Major bug fixes

• out_forward: Fix nil error after purge obsoleted socket in socket cache

Enjoy logging!

Read More

Fluentd v1.7.2 has been released

Hi users!

We have released v1.7.2. ChangeLog is here. This release includes several fixes.

in_tcp: Add security/client to restrict access

This is similar to in_forward. You can limit the client by host/network. Here is configuration example:

<source>
  @type tcp
  # other parameters...
  <security>
    <client>
      host app_server1.com
    </client>
    <client>
      host web_server1.com
    </client>
  </security>
</source>

With this configuration, in_tcp rejects the data from other hosts, e.g. app_server2.com.

Major bug fixes

• buf_file/buf_file_single: fix to handle compress data during restart
• plugin: Use __send__ to avoid conflict with user defined send method

Enjoy logging!

Read More

Fluentd v1.7.1 has been released

Hi users!

We have released v1.7.1. ChangeLog is here. This release includes several enhancements and fixes.

parser_syslog: Add string parser for rfc3164 message

v1.7.1 introduces parser_type parameter to choose internal implementation for rfc3164 message.

parser_syslog uses regexp parser to parse rfc3164 message by default but it doesn't work for some patterns, see this issue. string parser avoids this problem.

Here is a configuration example:

<source>
  @type syslog
  <parse>
    parser_type string
  </buffer>
  # other parameters...
</source>

string parser is 2x faster than regexp parser, so we recommend to use string parser for new deployment.

Major bug fixes

• buf_file/buf_file_single: fix to ignore placeholder based path during resume
• buf_file: Ensure to remove metadata file after buffer creation failure
• server helper: Ignore ETIMEDOUT error in SSL_accept

Enjoy logging!

Read More