Fluentd Blog https://www.fluentd.org/blog Get the Latest Updates on Fluentd and More td-agent v4.5.0 has been released https://www.fluentd.org/blog/td-agent-v4.5.0-has-been-released <p>Hi users!</p> <p>We have released td-agent <a href="https://github.com/fluent/fluent-package-builder/releases/tag/v4.5.0">v4.5.0</a>. td-agent is a stable distribution package of Fluentd.</p> <h3>Changes from td-agent v4.4.2</h3> <ul> <li>Update bundled Ruby to 2.7.8 which is the last version of Ruby 2.7 series. <ul> <li>Only for RHEL 9 &amp; Ubuntu 22.04 jammy, we updat Ruby to 3.1.4 exceptionally.</li> </ul></li> <li>Update fluentd to <a href="https://github.com/fluent/fluentd/releases/tag/v1.16.1">1.16.1</a></li> <li>Update plugins <ul> <li>fluent-plugin-kafka 0.19.0</li> <li>fluent-plugin-elasticsearch 5.3.0</li> <li>fluent-plugin-opensearch 1.1.0</li> </ul></li> <li>Drop Debian buster support</li> </ul> <h3>About next major version</h3> <p>We are preparing next major version of td-agent which bundles Ruby 3.2. It&#39;s still work in progerss, we&#39;ll announce it as soon as we are ready for it.</p> <p>Please note that the package name will be changed to <code>fluent-package</code>. Please see the following discussion for more detail: <a href="https://github.com/fluent/fluentd/discussions/3860">https://github.com/fluent/fluentd/discussions/3860</a></p> <h3>Download</h3> <p>Please see <a href="/download#td-agent">the download page</a>.</p> 2023-05-08 <p>Hi users!</p> <p>We have released td-agent <a href="https://github.com/fluent/fluent-package-builder/releases/tag/v4.5.0">v4.5.0</a>. td-agent is a stable distribution package of Fluentd.</p> <h3>Changes from td-agent v4.4.2</h3> <ul> <li>Update bundled Ruby to 2.7.8 which is the last version of Ruby 2.7 series. <ul> <li>Only for RHEL 9 &amp; Ubuntu 22.04 jammy, we updat Ruby to 3.1.4 exceptionally.</li> </ul></li> <li>Update fluentd to <a href="https://github.com/fluent/fluentd/releases/tag/v1.16.1">1.16.1</a></li> <li>Update plugins <ul> <li>fluent-plugin-kafka 0.19.0</li> <li>fluent-plugin-elasticsearch 5.3.0</li> <li>fluent-plugin-opensearch 1.1.0</li> </ul></li> <li>Drop Debian buster support</li> </ul> <h3>About next major version</h3> <p>We are preparing next major version of td-agent which bundles Ruby 3.2. It&#39;s still work in progerss, we&#39;ll announce it as soon as we are ready for it.</p> <p>Please note that the package name will be changed to <code>fluent-package</code>. Please see the following discussion for more detail: <a href="https://github.com/fluent/fluentd/discussions/3860">https://github.com/fluent/fluentd/discussions/3860</a></p> <h3>Download</h3> <p>Please see <a href="/download#td-agent">the download page</a>.</p> Fluentd v1.16.1 has been released https://www.fluentd.org/blog/fluentd-v1.16.1-has-been-released <p>Hi users!</p> <p>We have released v1.16.1 on 2023-04-17. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v1161---20230417">here</a>.</p> <p>In the previous version v1.16.0, there was a bug that caused Fluentd to fail to start with certain secondary configurations. In this release, we fixed that problem and added a new feature of <code>in_tcp</code>. And other some improvements!</p> <h2>Enhancement</h2> <ul> <li><code>in_tcp</code>: Add <code>message_length_limit</code> to drop large incoming data. <a href="https://github.com/fluent/fluentd/pull/4137">#4137</a></li> </ul> <h2>Bug Fixes</h2> <h3><code>out_secondary_file</code>: Fix NameError of <code>SecondaryFileOutput</code> when setting other secondaries</h3> <p>In the previous version v1.16.0, there was a bug that if you set another secondary without ever setting <code>out_secondary_file</code>, Fluentd fails to start with the following error.</p> <pre><code>/path/to/fluentd/lib/fluent/plugin/output.rb:429:in `configure&#39;: uninitialized constant Fluent::Plugin::Output::SecondaryFileOutput (NameError) if (@secondary.class != SecondaryFileOutput) &amp;&amp; ^^^^^^^^^^^^^^^^^^^ </code></pre> <p>In this release, we fixed this problem.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/4124">#4124</a> for more information.</p> <h3><code>Buffer</code>: Fix that <code>compress</code> setting causes unexpected error when receiving already compressed MessagePack</h3> <p>With this release, it is now possible that Fluentd forwards already compressed MessagePack data to another Fluentd as is (without decompressing).</p> <p>A possible use case is two-stage forwarding.</p> <p>Forwarder1(<code>out_forward</code>) -&gt; Forwarder2(<code>in_forward</code>, <code>out_forward</code>) -&gt; Aggregator(<code>in_forward</code>)</p> <p>In this case, Forwarder2 should process the data of <code>CompressedMessagePackEventStream</code> as is (without decompressing) and re-forward the data to Aggregator.</p> <p>Until this version, a bug prevented us from setting Forwarder2&#39;s <code>compress gzip</code> of <a href="https://docs.fluentd.org/output/forward#how-to-enable-gzip-compression">out_forward</a> or <a href="https://docs.fluentd.org/configuration/buffer-section#buffering-parameters">buffer</a>. It resulted in the following error.</p> <pre><code>[error]: #0 unexpected error on reading data host=&quot;...&quot; port=... error_class=ArgumentError error=&quot;unknown keyword: :packer&quot; </code></pre> <p>So we had no choice but to decompress and forward it from Forwarder2 to Aggregator.</p> <p>With this release, we can now set <code>compress gzip</code> for Forwarder2!</p> <p>See <a href="https://github.com/fluent/fluentd/issues/4146">#4146</a> and <a href="https://github.com/fluent/fluentd/pull/4147">#4147</a> for more information.</p> <h3>Others</h3> <ul> <li>Server helper: Suppress error of <code>UDPServer</code> over <code>max_bytes</code> on Windows. <a href="https://github.com/fluent/fluentd/pull/4131">#4131</a></li> </ul> <p>Enjoy logging!</p> 2023-04-20 <p>Hi users!</p> <p>We have released v1.16.1 on 2023-04-17. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v1161---20230417">here</a>.</p> <p>In the previous version v1.16.0, there was a bug that caused Fluentd to fail to start with certain secondary configurations. In this release, we fixed that problem and added a new feature of <code>in_tcp</code>. And other some improvements!</p> <h2>Enhancement</h2> <ul> <li><code>in_tcp</code>: Add <code>message_length_limit</code> to drop large incoming data. <a href="https://github.com/fluent/fluentd/pull/4137">#4137</a></li> </ul> <h2>Bug Fixes</h2> <h3><code>out_secondary_file</code>: Fix NameError of <code>SecondaryFileOutput</code> when setting other secondaries</h3> <p>In the previous version v1.16.0, there was a bug that if you set another secondary without ever setting <code>out_secondary_file</code>, Fluentd fails to start with the following error.</p> <pre><code>/path/to/fluentd/lib/fluent/plugin/output.rb:429:in `configure&#39;: uninitialized constant Fluent::Plugin::Output::SecondaryFileOutput (NameError) if (@secondary.class != SecondaryFileOutput) &amp;&amp; ^^^^^^^^^^^^^^^^^^^ </code></pre> <p>In this release, we fixed this problem.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/4124">#4124</a> for more information.</p> <h3><code>Buffer</code>: Fix that <code>compress</code> setting causes unexpected error when receiving already compressed MessagePack</h3> <p>With this release, it is now possible that Fluentd forwards already compressed MessagePack data to another Fluentd as is (without decompressing).</p> <p>A possible use case is two-stage forwarding.</p> <p>Forwarder1(<code>out_forward</code>) -&gt; Forwarder2(<code>in_forward</code>, <code>out_forward</code>) -&gt; Aggregator(<code>in_forward</code>)</p> <p>In this case, Forwarder2 should process the data of <code>CompressedMessagePackEventStream</code> as is (without decompressing) and re-forward the data to Aggregator.</p> <p>Until this version, a bug prevented us from setting Forwarder2&#39;s <code>compress gzip</code> of <a href="https://docs.fluentd.org/output/forward#how-to-enable-gzip-compression">out_forward</a> or <a href="https://docs.fluentd.org/configuration/buffer-section#buffering-parameters">buffer</a>. It resulted in the following error.</p> <pre><code>[error]: #0 unexpected error on reading data host=&quot;...&quot; port=... error_class=ArgumentError error=&quot;unknown keyword: :packer&quot; </code></pre> <p>So we had no choice but to decompress and forward it from Forwarder2 to Aggregator.</p> <p>With this release, we can now set <code>compress gzip</code> for Forwarder2!</p> <p>See <a href="https://github.com/fluent/fluentd/issues/4146">#4146</a> and <a href="https://github.com/fluent/fluentd/pull/4147">#4147</a> for more information.</p> <h3>Others</h3> <ul> <li>Server helper: Suppress error of <code>UDPServer</code> over <code>max_bytes</code> on Windows. <a href="https://github.com/fluent/fluentd/pull/4131">#4131</a></li> </ul> <p>Enjoy logging!</p> Fluentd v1.16.0 has been released https://www.fluentd.org/blog/fluentd-v1.16.0-has-been-released <p>Hi users!</p> <p>We have released v1.16.0 on 2023-03-29. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v1160---20230329">here</a>.</p> <p>This release is a new release of v1.16 series. In this release, we enhanced the feature for chunk file corruption and fixed some bugs, mainly about logging and race condition errors.</p> <h2>Enhancement</h2> <h3>Backup corrupted chunk files at resuming</h3> <p>Some chunk files in <a href="https://docs.fluentd.org/buffer/file">buffer_file</a> or <a href="https://docs.fluentd.org/buffer/file_single">buffer_file_single</a> are possibly corrupted after Fluentd stopped abnormally, such as due to a power failure.</p> <p>Fluentd has a feature to backup unrecoverable chunks as before. However, when Fluentd resumes, remaining corrupted chunk files were just deleted.</p> <p>Since this release, Fluentd also backups those files at resuming. In addition, Fluentd outputs some useful logs about possibly corrupted chunk files due to an abnormal termination.</p> <p>Please see <a href="https://docs.fluentd.org/buffer#detecting-chunk-file-corruption-when-fluentd-starts-up">the document</a> and the following PRs for more information.</p> <ul> <li><a href="https://github.com/fluent/fluentd/pull/4025">buffer: backup broken file chunk</a></li> <li><a href="https://github.com/fluent/fluentd/pull/4027">Add warning messages for restoring buffer with <code>flush_at_shutdown true</code></a></li> <li><a href="https://github.com/fluent/fluentd/pull/4028">Add logs for time period of restored buffer possibly broken</a></li> </ul> <h3><code>in_tcp</code>: Add <code>send_keepalive_packet</code> option</h3> <p>Since this release, you can use <a href="https://docs.fluentd.org/input/tcp#general-configuration">send_keepalive_packet option</a> for <code>in_tcp</code>, as well as <a href="https://docs.fluentd.org/input/forward">in_forward</a> or <a href="https://docs.fluentd.org/input/syslog">in_syslog</a>.</p> <p>Please see <a href="https://docs.fluentd.org/input/tcp#general-configuration">the document</a> and <a href="https://github.com/fluent/fluentd/pull/3961">#3961</a> for more information.</p> <h2>Bug Fixes</h2> <ul> <li><code>out_secondary_file</code>: Fix race condition. <a href="https://github.com/fluent/fluentd/pull/4081">#4081</a></li> <li><code>out_secondary_file</code>: Suppress warning using different secondary for out<em>secondary</em>file. <a href="https://github.com/fluent/fluentd/pull/4087">#4087</a></li> <li><code>out_forward</code>: Fix error of ack handling conflict with <code>require_ack_response</code>. <a href="https://github.com/fluent/fluentd/pull/4030">#4030</a></li> <li>Windows: Fix bug that Fluentd sometimes tries to use an unavailable port and fails to start. <a href="https://github.com/fluent/fluentd/pull/4092">#4092</a></li> <li>Windows: Fix bug that flushing or graceful reloading cause reopening wrong log file. <a href="https://github.com/fluent/fluentd/pull/4054">#4054</a></li> <li>Fix not to log some initial messages without <code>format</code> setting applied. <a href="https://github.com/fluent/fluentd/pull/4091">#4091</a></li> <li>Fix bug that some <code>system</code> configs are not reflected. <a href="https://github.com/fluent/fluentd/pull/4064">#4064</a>, <a href="https://github.com/fluent/fluentd/pull/4065">#4065</a> <ul> <li><a href="https://docs.fluentd.org/deployment/system-config#suppress_repeated_stacktrace">suppress_repeated_stacktrace</a></li> <li><a href="https://docs.fluentd.org/deployment/system-config#ignore_same_log_interval">ignore_same_log_interval</a> (It was not reflected only to the supervisor process)</li> </ul></li> <li>Non-Windows: Fix not to generate sigdump file after receiving <code>SIGTERM</code>. <a href="https://github.com/fluent/fluentd/pull/4043">#4043</a></li> <li>Fix bug that <code>system_config.workers</code> value can be wrongly <code>1</code> at config check at startup. <a href="https://github.com/fluent/fluentd/pull/4066">#4066</a></li> <li>Fix bug that a variable whose type is not <code>Fluent::Config::Element</code> can be passed to <code>Fluent::Plugin::Base::configure()</code>. <a href="https://github.com/fluent/fluentd/pull/4066">#4066</a></li> </ul> <p>Enjoy logging!</p> 2023-03-29 <p>Hi users!</p> <p>We have released v1.16.0 on 2023-03-29. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v1160---20230329">here</a>.</p> <p>This release is a new release of v1.16 series. In this release, we enhanced the feature for chunk file corruption and fixed some bugs, mainly about logging and race condition errors.</p> <h2>Enhancement</h2> <h3>Backup corrupted chunk files at resuming</h3> <p>Some chunk files in <a href="https://docs.fluentd.org/buffer/file">buffer_file</a> or <a href="https://docs.fluentd.org/buffer/file_single">buffer_file_single</a> are possibly corrupted after Fluentd stopped abnormally, such as due to a power failure.</p> <p>Fluentd has a feature to backup unrecoverable chunks as before. However, when Fluentd resumes, remaining corrupted chunk files were just deleted.</p> <p>Since this release, Fluentd also backups those files at resuming. In addition, Fluentd outputs some useful logs about possibly corrupted chunk files due to an abnormal termination.</p> <p>Please see <a href="https://docs.fluentd.org/buffer#detecting-chunk-file-corruption-when-fluentd-starts-up">the document</a> and the following PRs for more information.</p> <ul> <li><a href="https://github.com/fluent/fluentd/pull/4025">buffer: backup broken file chunk</a></li> <li><a href="https://github.com/fluent/fluentd/pull/4027">Add warning messages for restoring buffer with <code>flush_at_shutdown true</code></a></li> <li><a href="https://github.com/fluent/fluentd/pull/4028">Add logs for time period of restored buffer possibly broken</a></li> </ul> <h3><code>in_tcp</code>: Add <code>send_keepalive_packet</code> option</h3> <p>Since this release, you can use <a href="https://docs.fluentd.org/input/tcp#general-configuration">send_keepalive_packet option</a> for <code>in_tcp</code>, as well as <a href="https://docs.fluentd.org/input/forward">in_forward</a> or <a href="https://docs.fluentd.org/input/syslog">in_syslog</a>.</p> <p>Please see <a href="https://docs.fluentd.org/input/tcp#general-configuration">the document</a> and <a href="https://github.com/fluent/fluentd/pull/3961">#3961</a> for more information.</p> <h2>Bug Fixes</h2> <ul> <li><code>out_secondary_file</code>: Fix race condition. <a href="https://github.com/fluent/fluentd/pull/4081">#4081</a></li> <li><code>out_secondary_file</code>: Suppress warning using different secondary for out<em>secondary</em>file. <a href="https://github.com/fluent/fluentd/pull/4087">#4087</a></li> <li><code>out_forward</code>: Fix error of ack handling conflict with <code>require_ack_response</code>. <a href="https://github.com/fluent/fluentd/pull/4030">#4030</a></li> <li>Windows: Fix bug that Fluentd sometimes tries to use an unavailable port and fails to start. <a href="https://github.com/fluent/fluentd/pull/4092">#4092</a></li> <li>Windows: Fix bug that flushing or graceful reloading cause reopening wrong log file. <a href="https://github.com/fluent/fluentd/pull/4054">#4054</a></li> <li>Fix not to log some initial messages without <code>format</code> setting applied. <a href="https://github.com/fluent/fluentd/pull/4091">#4091</a></li> <li>Fix bug that some <code>system</code> configs are not reflected. <a href="https://github.com/fluent/fluentd/pull/4064">#4064</a>, <a href="https://github.com/fluent/fluentd/pull/4065">#4065</a> <ul> <li><a href="https://docs.fluentd.org/deployment/system-config#suppress_repeated_stacktrace">suppress_repeated_stacktrace</a></li> <li><a href="https://docs.fluentd.org/deployment/system-config#ignore_same_log_interval">ignore_same_log_interval</a> (It was not reflected only to the supervisor process)</li> </ul></li> <li>Non-Windows: Fix not to generate sigdump file after receiving <code>SIGTERM</code>. <a href="https://github.com/fluent/fluentd/pull/4043">#4043</a></li> <li>Fix bug that <code>system_config.workers</code> value can be wrongly <code>1</code> at config check at startup. <a href="https://github.com/fluent/fluentd/pull/4066">#4066</a></li> <li>Fix bug that a variable whose type is not <code>Fluent::Config::Element</code> can be passed to <code>Fluent::Plugin::Base::configure()</code>. <a href="https://github.com/fluent/fluentd/pull/4066">#4066</a></li> </ul> <p>Enjoy logging!</p> Fluentd v1.15.3 has been released https://www.fluentd.org/blog/fluentd-v1.15.3-has-been-released <p>Hi users!</p> <p>We have released v1.15.3 on 2022-11-02. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v1153---20221102">here</a>.</p> <p>In this release, we fixed several bugs.</p> <h2>Bug Fixes</h2> <h3><code>out_file</code>: Fix the multi-worker check with <code>&lt;worker N-M&gt;</code> directive</h3> <p>In the v1.15.1, we added a new feature to prevent write conflicts between multiple workers.</p> <ul> <li><a href="https://github.com/fluent/fluentd/pull/3808">#3808</a></li> </ul> <p>However, this fix didn&#39;t work correctly with <code>&lt;worker N-M&gt;</code> directive.</p> <ul> <li><a href="https://docs.fluentd.org/deployment/multi-process-workers#less-than-worker-n-m-greater-than-directive"><code>&lt;worker N-M&gt;</code> directive</a></li> </ul> <p>With this setting, the configuration check before starting the supervisor mistakenly determines that the setting of <code>out_file</code> is invalid and causes Fluentd to terminate.</p> <p>In this release, we fixed this problem.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/3942">#3942</a> for more information.</p> <h3>Fix log rotation on Windows</h3> <p>We can configure log rotation setting as follows.</p> <ul> <li><a href="https://docs.fluentd.org/deployment/logging#log-rotation-setting">Log Rotation Setting</a></li> </ul> <p>On Windows, the log files must be separated by each process.</p> <blockquote> <p>NOTE: When --log-rotate-age is specified on Windows, log files are separated into log-supervisor-0.log, log-0.log, ..., log-N.log where N is generation - 1 due to the system limitation. Windows does not permit delete and rename files simultaneously owned by another process.</p> </blockquote> <p>However, that log rotation setting in the system-directive didn&#39;t satisfy this and Fluentd outputted the logs of the supervisor process into the log file of the worker-0 process.</p> <p>This could cause errors during log rotation.</p> <p>In this release, we fixed this problem.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/3939">#3939</a> for more information.</p> <h3>Support glob for <code>!include</code> directive in YAML config format</h3> <p>In the v1.15.0, we supported YAML config format.</p> <ul> <li><a href="https://docs.fluentd.org/configuration/config-file-yaml">Config File Syntax (YAML)</a></li> <li><a href="https://github.com/fluent/fluentd/pull/3712">#3712</a></li> </ul> <p>However, handling glob of <code>!include</code> directive was leaked.</p> <p>In this release, we supported it.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/3917">#3917</a> for more information.</p> <h3>Remove meaningless and unsecure <code>oj</code> options</h3> <p>In this release, we removed the following <code>oj</code> options.</p> <ul> <li><code>FLUENT_OJ_OPTION_MODE=object</code></li> <li><code>FLUENT_OJ_OPTION_MAX_NESTING</code></li> </ul> <p><code>FLUENT_OJ_OPTION_MODE=object</code> was unsecure, so we removed it.</p> <ul> <li><a href="https://github.com/fluent/fluentd/security/advisories/GHSA-fppq-mj76-fpj2">GHSA-fppq-mj76-fpj2</a></li> </ul> <p>This option is not used unless a user explicitly sets the environmental variable, so almost all users do not need to care about this vulnerability.</p> <p><code>FLUENT_OJ_OPTION_MAX_NESTING</code> was not supported, so we removed it.</p> <ul> <li><a href="https://github.com/fluent/fluentd/issues/3311#issuecomment-923741031">https://github.com/fluent/fluentd/issues/3311#issuecomment-923741031</a></li> </ul> <p>See <a href="https://github.com/fluent/fluentd/pull/3929">#3929</a> for more information.</p> <p>Enjoy logging!</p> 2022-11-11 <p>Hi users!</p> <p>We have released v1.15.3 on 2022-11-02. ChangeLog is <a href="https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v1153---20221102">here</a>.</p> <p>In this release, we fixed several bugs.</p> <h2>Bug Fixes</h2> <h3><code>out_file</code>: Fix the multi-worker check with <code>&lt;worker N-M&gt;</code> directive</h3> <p>In the v1.15.1, we added a new feature to prevent write conflicts between multiple workers.</p> <ul> <li><a href="https://github.com/fluent/fluentd/pull/3808">#3808</a></li> </ul> <p>However, this fix didn&#39;t work correctly with <code>&lt;worker N-M&gt;</code> directive.</p> <ul> <li><a href="https://docs.fluentd.org/deployment/multi-process-workers#less-than-worker-n-m-greater-than-directive"><code>&lt;worker N-M&gt;</code> directive</a></li> </ul> <p>With this setting, the configuration check before starting the supervisor mistakenly determines that the setting of <code>out_file</code> is invalid and causes Fluentd to terminate.</p> <p>In this release, we fixed this problem.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/3942">#3942</a> for more information.</p> <h3>Fix log rotation on Windows</h3> <p>We can configure log rotation setting as follows.</p> <ul> <li><a href="https://docs.fluentd.org/deployment/logging#log-rotation-setting">Log Rotation Setting</a></li> </ul> <p>On Windows, the log files must be separated by each process.</p> <blockquote> <p>NOTE: When --log-rotate-age is specified on Windows, log files are separated into log-supervisor-0.log, log-0.log, ..., log-N.log where N is generation - 1 due to the system limitation. Windows does not permit delete and rename files simultaneously owned by another process.</p> </blockquote> <p>However, that log rotation setting in the system-directive didn&#39;t satisfy this and Fluentd outputted the logs of the supervisor process into the log file of the worker-0 process.</p> <p>This could cause errors during log rotation.</p> <p>In this release, we fixed this problem.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/3939">#3939</a> for more information.</p> <h3>Support glob for <code>!include</code> directive in YAML config format</h3> <p>In the v1.15.0, we supported YAML config format.</p> <ul> <li><a href="https://docs.fluentd.org/configuration/config-file-yaml">Config File Syntax (YAML)</a></li> <li><a href="https://github.com/fluent/fluentd/pull/3712">#3712</a></li> </ul> <p>However, handling glob of <code>!include</code> directive was leaked.</p> <p>In this release, we supported it.</p> <p>See <a href="https://github.com/fluent/fluentd/pull/3917">#3917</a> for more information.</p> <h3>Remove meaningless and unsecure <code>oj</code> options</h3> <p>In this release, we removed the following <code>oj</code> options.</p> <ul> <li><code>FLUENT_OJ_OPTION_MODE=object</code></li> <li><code>FLUENT_OJ_OPTION_MAX_NESTING</code></li> </ul> <p><code>FLUENT_OJ_OPTION_MODE=object</code> was unsecure, so we removed it.</p> <ul> <li><a href="https://github.com/fluent/fluentd/security/advisories/GHSA-fppq-mj76-fpj2">GHSA-fppq-mj76-fpj2</a></li> </ul> <p>This option is not used unless a user explicitly sets the environmental variable, so almost all users do not need to care about this vulnerability.</p> <p><code>FLUENT_OJ_OPTION_MAX_NESTING</code> was not supported, so we removed it.</p> <ul> <li><a href="https://github.com/fluent/fluentd/issues/3311#issuecomment-923741031">https://github.com/fluent/fluentd/issues/3311#issuecomment-923741031</a></li> </ul> <p>See <a href="https://github.com/fluent/fluentd/pull/3929">#3929</a> for more information.</p> <p>Enjoy logging!</p> td-agent v4.4.2 has been released https://www.fluentd.org/blog/td-agent-v4.4.2-has-been-released <p>Hi users!</p> <p>We have released td-agent <a href="https://github.com/fluent/fluent-package-builder/releases/tag/v4.4.2">v4.4.2</a>. td-agent is a stable distribution package of Fluentd.</p> <h3>Changes from td-agent v4.4.1</h3> <ul> <li>Update fluentd to <a href="https://github.com/fluent/fluentd/releases/tag/v1.15.3">1.15.3</a> <ul> <li>Fix log initializer to correctly create per-process files on Windows</li> <li>out_file: Fix the multi-worker check with <code>&lt;worker 0-N&gt;</code> directive</li> <li>Remove meaningless oj options</li> <li>Support glob for <code>!include</code> directive in YAML config format</li> </ul></li> <li>macOS: Support Apple Silicon</li> <li>Update plugins <ul> <li>fluent-plugin-elasticsearch 5.2.4</li> <li>fluent-plugin-opensearch 1.0.8</li> <li>fluent-plugin-s3 1.7.2</li> <li>fluent-plugin-windows-eventlog 0.8.2</li> </ul></li> </ul> <h3>Download</h3> <p>Please see <a href="/download#td-agent">the download page</a>.</p> 2022-11-08 <p>Hi users!</p> <p>We have released td-agent <a href="https://github.com/fluent/fluent-package-builder/releases/tag/v4.4.2">v4.4.2</a>. td-agent is a stable distribution package of Fluentd.</p> <h3>Changes from td-agent v4.4.1</h3> <ul> <li>Update fluentd to <a href="https://github.com/fluent/fluentd/releases/tag/v1.15.3">1.15.3</a> <ul> <li>Fix log initializer to correctly create per-process files on Windows</li> <li>out_file: Fix the multi-worker check with <code>&lt;worker 0-N&gt;</code> directive</li> <li>Remove meaningless oj options</li> <li>Support glob for <code>!include</code> directive in YAML config format</li> </ul></li> <li>macOS: Support Apple Silicon</li> <li>Update plugins <ul> <li>fluent-plugin-elasticsearch 5.2.4</li> <li>fluent-plugin-opensearch 1.0.8</li> <li>fluent-plugin-s3 1.7.2</li> <li>fluent-plugin-windows-eventlog 0.8.2</li> </ul></li> </ul> <h3>Download</h3> <p>Please see <a href="/download#td-agent">the download page</a>.</p>