Fluentd Blog https://www.fluentd.org/blog Get the Latest Updates on Fluentd and More Drop schedule announcement in 2019 https://www.fluentd.org/blog/drop-schedule-announcement-in-2019 <p>Hi users and developers!</p> <p>We announce the drop schedule for Fluentd development.</p> <h2>Fluentd</h2> <p>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.</p> <ul> <li>Stop to accept security fix patches</li> <li>Stop to update docker images</li> <li>Stop to handle v0.12 issues/questions</li> </ul> <p>We recommend plugin developers to use v1 API for full v1 feature support :)</p> <h2>Treasure Agent(td-agent)</h2> <p>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.</p> <p>Of course, we recommend to use td-agent 3, fluentd v1 serise, for new deployment :)</p> <h2>Ruby</h2> <p>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.</p> <ul> <li>td-agent 2.5 uses ruby 2.5</li> <li>td-agent 3 uses ruby 2.4</li> <li>td-agent 4 will use ruby 2.6</li> <li>Alpine docker images use ruby 2.5</li> <li>Debian docker images use ruby 2.6</li> <li>Latest OSes(CentOS 8, Ubuntu 18.04, Debian 10, etc) use ruby 2.4 or later</li> </ul> <p>In addition, we can use rvm/rbenv to install any ruby version, so we hope dropping ruby 2.3 or earlier doesn&#39;t have big impact for existing users.</p> <p>If you have any question, post it to mailing list ;)</p> 2019-11-06 <p>Hi users and developers!</p> <p>We announce the drop schedule for Fluentd development.</p> <h2>Fluentd</h2> <p>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.</p> <ul> <li>Stop to accept security fix patches</li> <li>Stop to update docker images</li> <li>Stop to handle v0.12 issues/questions</li> </ul> <p>We recommend plugin developers to use v1 API for full v1 feature support :)</p> <h2>Treasure Agent(td-agent)</h2> <p>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.</p> <p>Of course, we recommend to use td-agent 3, fluentd v1 serise, for new deployment :)</p> <h2>Ruby</h2> <p>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.</p> <ul> <li>td-agent 2.5 uses ruby 2.5</li> <li>td-agent 3 uses ruby 2.4</li> <li>td-agent 4 will use ruby 2.6</li> <li>Alpine docker images use ruby 2.5</li> <li>Debian docker images use ruby 2.6</li> <li>Latest OSes(CentOS 8, Ubuntu 18.04, Debian 10, etc) use ruby 2.4 or later</li> </ul> <p>In addition, we can use rvm/rbenv to install any ruby version, so we hope dropping ruby 2.3 or earlier doesn&#39;t have big impact for existing users.</p> <p>If you have any question, post it to mailing list ;)</p> Fluentd v1.7.4 has been released https://www.fluentd.org/blog/fluentd-v1.7.4-has-been-released <p>Hi users!</p> <p>We have released v1.7.4. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release is mainly for fixing bugs.</p> <h3>in_http: Add <code>use_204_response</code> parameter</h3> <p>This change follows RFC7231. For zero-length payload, <code>204</code> is better than <code>200</code>.</p> <pre><code>&lt;source&gt; @type http # other parameters use_204_response true &lt;/source&gt; </code></pre> <p>This parameter will be removed at fluentd v2 and <code>in_http</code> will return <code>204</code>.</p> <h3>Major bug fixes</h3> <ul> <li>child_process helper: fix stderr blocking for discard case</li> <li>log: Fix log rotation handling on Windows. This changes log filename. See <a href="https://docs.fluentd.org/deployment/logging#log-rotation-setting">https://docs.fluentd.org/deployment/logging#log-rotation-setting</a></li> </ul> <p>Enjoy logging!</p> 2019-10-24 <p>Hi users!</p> <p>We have released v1.7.4. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release is mainly for fixing bugs.</p> <h3>in_http: Add <code>use_204_response</code> parameter</h3> <p>This change follows RFC7231. For zero-length payload, <code>204</code> is better than <code>200</code>.</p> <pre><code>&lt;source&gt; @type http # other parameters use_204_response true &lt;/source&gt; </code></pre> <p>This parameter will be removed at fluentd v2 and <code>in_http</code> will return <code>204</code>.</p> <h3>Major bug fixes</h3> <ul> <li>child_process helper: fix stderr blocking for discard case</li> <li>log: Fix log rotation handling on Windows. This changes log filename. See <a href="https://docs.fluentd.org/deployment/logging#log-rotation-setting">https://docs.fluentd.org/deployment/logging#log-rotation-setting</a></li> </ul> <p>Enjoy logging!</p> Fluentd v1.7.3 has been released https://www.fluentd.org/blog/fluentd-v1.7.3-has-been-released <p>Hi users!</p> <p>We have released v1.7.3. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release is mainly for fixing socket cache bug of out_forward.</p> <h3>in_syslog: Replace <code>priority_key</code> with <code>severity_key</code></h3> <p><code>in_syslog</code>&#39;s <code>priority_key</code> parameter is misleading name because it sets severity, not priority value. So we add <code>severity_key</code> parameter.</p> <pre><code>&lt;source&gt; @type syslog severity_key severity tag syslog &lt;/source&gt; </code></pre> <p><code>priority_key</code> is still supported for existing users but we will remove <code>priority_key</code> parameter at fluentd v2.</p> <h3>Major bug fixes</h3> <ul> <li>out_forward: Fix <code>nil</code> error after purge obsoleted socket in socket cache</li> </ul> <p>Enjoy logging!</p> 2019-10-01 <p>Hi users!</p> <p>We have released v1.7.3. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release is mainly for fixing socket cache bug of out_forward.</p> <h3>in_syslog: Replace <code>priority_key</code> with <code>severity_key</code></h3> <p><code>in_syslog</code>&#39;s <code>priority_key</code> parameter is misleading name because it sets severity, not priority value. So we add <code>severity_key</code> parameter.</p> <pre><code>&lt;source&gt; @type syslog severity_key severity tag syslog &lt;/source&gt; </code></pre> <p><code>priority_key</code> is still supported for existing users but we will remove <code>priority_key</code> parameter at fluentd v2.</p> <h3>Major bug fixes</h3> <ul> <li>out_forward: Fix <code>nil</code> error after purge obsoleted socket in socket cache</li> </ul> <p>Enjoy logging!</p> Fluentd v1.7.2 has been released https://www.fluentd.org/blog/fluentd-v1.7.2-has-been-released <p>Hi users!</p> <p>We have released v1.7.2. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release includes several fixes.</p> <h3>in_tcp: Add <code>security/client</code> to restrict access</h3> <p>This is similar to <code>in_forward</code>. You can limit the client by host/network. Here is configuration example:</p> <pre><code>&lt;source&gt; @type tcp # other parameters... &lt;security&gt; &lt;client&gt; host app_server1.com &lt;/client&gt; &lt;client&gt; host web_server1.com &lt;/client&gt; &lt;/security&gt; &lt;/source&gt; </code></pre> <p>With this configuration, <code>in_tcp</code> rejects the data from other hosts, e.g. <code>app_server2.com</code>.</p> <h3>Major bug fixes</h3> <ul> <li>buf_file/buf_file_single: fix to handle compress data during restart</li> <li>plugin: Use <code>__send__</code> to avoid conflict with user defined <code>send</code> method</li> </ul> <p>Enjoy logging!</p> 2019-09-19 <p>Hi users!</p> <p>We have released v1.7.2. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release includes several fixes.</p> <h3>in_tcp: Add <code>security/client</code> to restrict access</h3> <p>This is similar to <code>in_forward</code>. You can limit the client by host/network. Here is configuration example:</p> <pre><code>&lt;source&gt; @type tcp # other parameters... &lt;security&gt; &lt;client&gt; host app_server1.com &lt;/client&gt; &lt;client&gt; host web_server1.com &lt;/client&gt; &lt;/security&gt; &lt;/source&gt; </code></pre> <p>With this configuration, <code>in_tcp</code> rejects the data from other hosts, e.g. <code>app_server2.com</code>.</p> <h3>Major bug fixes</h3> <ul> <li>buf_file/buf_file_single: fix to handle compress data during restart</li> <li>plugin: Use <code>__send__</code> to avoid conflict with user defined <code>send</code> method</li> </ul> <p>Enjoy logging!</p> Fluentd v1.7.1 has been released https://www.fluentd.org/blog/fluentd-v1.7.1-has-been-released <p>Hi users!</p> <p>We have released v1.7.1. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release includes several enhancements and fixes.</p> <h3>parser_syslog: Add <code>string</code> parser for rfc3164 message</h3> <p>v1.7.1 introduces <code>parser_type</code> parameter to choose internal implementation for <code>rfc3164</code> message.</p> <p><code>parser_syslog</code> uses <code>regexp</code> parser to parse rfc3164 message by default but it doesn&#39;t work for some patterns, see <a href="https://github.com/fluent/fluentd/issues/2585">this issue</a>. <code>string</code> parser avoids this problem.</p> <p>Here is a configuration example:</p> <pre><code>&lt;source&gt; @type syslog &lt;parse&gt; parser_type string &lt;/buffer&gt; # other parameters... &lt;/source&gt; </code></pre> <p><code>string</code> parser is 2x faster than <code>regexp</code> parser, so we recommend to use <code>string</code> parser for new deployment.</p> <h3>Major bug fixes</h3> <ul> <li>buf_file/buf_file_single: fix to ignore placeholder based path during resume</li> <li>buf_file: Ensure to remove metadata file after buffer creation failure</li> <li>server helper: Ignore <code>ETIMEDOUT</code> error in <code>SSL_accept</code></li> </ul> <p>Enjoy logging!</p> 2019-09-08 <p>Hi users!</p> <p>We have released v1.7.1. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md">here</a>. This release includes several enhancements and fixes.</p> <h3>parser_syslog: Add <code>string</code> parser for rfc3164 message</h3> <p>v1.7.1 introduces <code>parser_type</code> parameter to choose internal implementation for <code>rfc3164</code> message.</p> <p><code>parser_syslog</code> uses <code>regexp</code> parser to parse rfc3164 message by default but it doesn&#39;t work for some patterns, see <a href="https://github.com/fluent/fluentd/issues/2585">this issue</a>. <code>string</code> parser avoids this problem.</p> <p>Here is a configuration example:</p> <pre><code>&lt;source&gt; @type syslog &lt;parse&gt; parser_type string &lt;/buffer&gt; # other parameters... &lt;/source&gt; </code></pre> <p><code>string</code> parser is 2x faster than <code>regexp</code> parser, so we recommend to use <code>string</code> parser for new deployment.</p> <h3>Major bug fixes</h3> <ul> <li>buf_file/buf_file_single: fix to ignore placeholder based path during resume</li> <li>buf_file: Ensure to remove metadata file after buffer creation failure</li> <li>server helper: Ignore <code>ETIMEDOUT</code> error in <code>SSL_accept</code></li> </ul> <p>Enjoy logging!</p>