Release Version</th>	Release Date</th>	End of life</th> </tr>
v5.0.x (LTS)</td>	Aug, 2023</td>	Dec, 2025</td> </tr>
v6.0.0 (LTS)</td>	Aug, 2025</td>	Dec, 2027 (T.B.D.)</td> </tr>
v7.0.0 (LTS)</td>	Aug, 2027 (T.B.D.)</td>	T.B.D.</td> </tr> </table> Happy logging!</p> Fluentd v1.16.6 has been released 2024-08-20 Hi users!</p> We have released v1.16.6 on 2024-08-20. ChangeLog is here</a>.</p> This release is a maintenance release of v1.16 series. In this release, some bugs were fixed with backporting from v1.17.x.</p> Bug Fixes</h2> `yaml_parser</code>: $log_level</code> notation in YAML was supported</h3>`In this release, we added a support for $log_level</code> in YAML config file syntax</a>.</p> In the previous versions, if you used log_level</code> in YAML configuration, it causes a following warning:</p> [warn]: #0 'log_level' is deprecated parameter name. use '@log_level' instead. </code></pre> But @log_level</code> is invalid in YAML format. In YAML format, it should be $log_level</code> as same as similar parameter such as $tag</code> and $type</code>, but not supported before.</p> Since Fluentd v1.16.6, $log_level</code> has been supported! (In v1.17.x, it was supported since v1.17.1)</p> fluentd command: Fix --plugin</code> (-p) option not to overwrite default value</h3> In this release, we have fixed a bug that fluentd command: --plugin</code> (-p) option could not overwrite default value.</p> This bug was unexpectedly introduced since v1.16.0.</p> Now it was reverted to the original behavior.</p> logger: Fix LoadError with console gem v1.25</h3> In this release, we fixed a LoadError with console gem v1.25 or later.</p> Since console gem v1.25 or later, it's internal change causes a LoadError in Fluentd. This error breaks existing plugin such as fluent-plugin-prometheus which provides monitoring REST API.</p> 500 response when scraping prometheus metrics in kubernetes with istio service mesh</a></li> </ul> With supporting console gem v1.25 or later, this issue has solved!</p> Enjoy logging!</p> Fluentd v1.17.1 has been released 2024-08-19 Hi users!</p> We have released v1.17.1 on 2024-08-19. ChangeLog is here</a>.</p> This release is a new release of v1.17 series. In this release, we added some new options for some plugins and fixed bugs of Parser.</p> Enhancement</h2> yaml_parser</code>: $log_level</code> notation in YAML was supported</h3> In this release, we added a support for $log_level</code> in YAML config file syntax</a>.</p> In the previous versions, if you used log_level</code> in YAML configuration, it causes a following warning:</p> [warn]: #0 'log_level' is deprecated parameter name. use '@log_level' instead. </code></pre> But @log_level</code> is invalid in YAML format. In YAML format, it should be $log_level</code> as same as similar parameter such as $tag</code> and $type</code>, but not supported before.</p> Since Fluentd v1.17.1, $log_level</code> has been supported now!</p> out_http</code>: compress</code> option was supported</h3> In this release, we added a new option compress</a> for the out_http</a> plugin.</p> You can compress HTTP request body by specifying compress gzip</code>. To keep compatibility, the default configuration is set as compress text</code> (no compression).</p> This feature was contributed by @rockliffelewis. Thanks!</p> in_sample</code>: the default behavior was changed</h3> In this release, we changed the default behavior of in_sample</a> plugin and added a new option reuse_record</a> for it.</p> The default behavior has changed to copy sample data to avoid the impact of destructive changes by subsequent plugins.</p> In the previous versions, when in_sample</code> plugin is used with the subsequent filter parser plugin which uses remove_key_name_field</code>, it raises the following error repeatedly.</p> #0 dump an error event: error_class=ArgumentError error="message does not exist" </code></pre> This error occurs when key_name</code> and remove_key_name_field</code> removes key from record with destructive change in filter parser. It affects generated sample data after twice or later. (This error is not limited to filter parser plugin. The similar destructive change will be done with the subsequent plugins, this error is reproducible)</p> The new default behavior (reuse_record false</code>) avoids this problem, but it increases the load when generating large amounts of sample data. You can use this new parameter to have the same performance as before with reuse_record</code>.</p> Bug Fixes</h2> logger: Fix LoadError with console gem v1.25</h3> In this release, we fixed a LoadError with console gem v1.25 or later.</p> Since console gem v1.25 or later, it's internal change causes a LoadError in Fluentd. This error breaks existing plugin such as fluent-plugin-prometheus which provides monitoring REST API.</p> 500 response when scraping prometheus metrics in kubernetes with istio service mesh</a></li> </ul> With supporting console gem v1.25 or later, this issue has solved!</p> Enjoy logging!</p> fluent-package v5.1.0 has been released 2024-08-02 Hi users!</p> We have released fluent-package v5.1.0</a>. fluent-package is a stable distribution package of Fluentd. (successor of td-agent v4)</p> This release is a new release of v5.1 series. Bundled ruby version was upgraded to 3.2.5 and fluentd v1.17.0 was shipped!</p> Changes from fluent-package v5.0.4</h3> In this release, focused on updating bundled ones.</p> Update fluentd to 1.17.0</li> Update ruby to 3.2.5</li> Update bundled gems overall</li> </ul> Update bundled components overall</h3> In LTS version, conservative updating policy is enabled, so updating gem is very limited to bug fix or security fix. In contrast to LTS version, v5.1.0 bundles more recent components because of standard version.</p> As we already announced in Scheduled support lifecycle announcement about Fluent Package</a> blog article, in normal release channel, we will ship the latest version (v1.17.0) of Fluentd.</p> So if you want to try using latest version of Fluentd, v5.1.0 is one for you. If you use fluent-package in enterprise services, keep using fluent-package 5.0.x (LTS).</p> </i> Note:</b>In the previous versions, there is no different in normal release channel and LTS release channel. But from this release, v5.1.x will be shipped in normal release channel. v5.0.x will be shipped in LTS channel. </div> Download</h3> Please see the download page</a>.</p> About next LTS schedule</h4> We plan to ship the next LTS version of fluent-package v5.0.5 on Oct, 2024. The content of updates are still in T.B.D.</p> End of support for td-agent v4, let's migrate to fluent-package</h4> As it was already announced Drop schedule announcement about EOL of Treasure Agent (td-agent) 4</a>, td-agent v4 was reached EOL in Dec, 2023.</p> After reached EOL, td-agent v4.5.3 on Windows was released because there was a crash bug during startup on Windows. It was backported fix from fluent-package v5 as it is critical in some case. Even though this was a exceptional maintenance release, but there is no change to the fact that we already stopped maintaining td-agent v4.</p> We strongly recommend migrating from td-agent v4 to fluent-package v5 (LTS). See Upgrade to fluent-package v5</a></p>

Fluentd Blog

Drop Alpine and switch default to Debian for Fluentd docker image

2025-03-14

Hi users!</p>

We have planned to change what docker image provides.</p>

Currently, we ship Fluentd docker image for Alpine and Debian (armhf, arm64, amd64). But, Alpine image in Fluentd was already marked as deprecated, so we will make things forward.</p>

In the near future, we will drop Alpine image. This decision affects existing Alpine image users.</p>

Notice about existing Alpine image users</h2>

fluent/fluentd:edge</code> will be changed from Alpine to Debian image This is a notable incompatible change!</li> </ul></li> v1.19 (not released yet) No more releases for Alpine images</li> Then short tag also changed to Debian images (e.g. v1.19.0-1.0, v1.19-1 should be Debian instead of Alpine)</li> </ul></li> v1.18 Alpine image will not be supported after v1.19 is released (T.B.D.), so recommend to migrate it!</li> v1.16 Alpine image will be supported until Dec 2025, so there is room to migrate gradually.</li> </ul> If you still want to use Alpine, keep v1.16 series or v1.18 series. (not recommended though)</p> Why not provide Alpine anymore?</h2> It was well known that Alpine has possibility of incompatibility and performance issues in contrast to Debian images. It was a historical reason to provide Alpine images - "In the previous versions, we provided them", so there is no positive reason to continue it.</p> Provide shorter tags to follow internal version bump</h2> Not only just dropping Alpine image, we will improve tagging rules:</p> Add version-specific tag which will not be affected by internal version bump</li> </ul> In previous versions, there was no version-specific tag which would follow internal version bump. For example, if you want to stick to Fluentd v1.18.0, you can select v1.18.0-1.0, but if internal version was bumped to v1.18.0-1.1 or something, need to update it. There is edge-debian</code> tag, but it does not stick to a specific Fluentd version because it will automatically update when the next major/minor version is released.</p> For such a purpose, shorter v1.19 or v1.19.x tag will be available in the future release.</p> Happy logging!</p>



fluent-package v5.0.6 has been released
2025-02-14
Hi users!</p>

We have released fluent-package v5.0.6</a>.
fluent-package is a stable distribution package of Fluentd. (successor of td-agent v4)</p>

This is a maintenance release of v5.0.x LTS series.
Bundled Fluentd was updated to 1.16.7.</p>

We recommend upgrading to fluent-package v5.0.6!</p>

Changes from fluent-package v5.0.5</h2>

In this release, known Windows issues were fixed.</p>


Update bundled Fluentd to v1.16.7</li>
Update bundled gems overall</li>
msi: Fixed to keep some registry values with update</li>
</ul>

msi: Fixed to keep some registry values with update</h2>

In the previous versions, there had been a known issue that fluent-package 
could not keep some registry values when upgrading.</p>

Thus, if you modify Fluentd service (fluentdwinsvc</code>) related registry,
you need to restore your configuration after upgrading.</p>

Since v5.0.6, fluent-package was fixed to keep some registry values during upgrading package.</p>

Here is the target registry which will be kept during upgrading fluent-package:</p>


Start</code></li>
DelayedAutostart</code></li>
fluentdopt</code> (logging path might be modified by users)</li>
</ul>

In most cases, fluent-package user might want to keep fluentdopt</code> because
it stores additional command line option parameters.</p>

In this release, bundled Fluentd v1.16.7 also contains the fixes for Windows.</p>


Windows: Fix NoMethodError</code> of --daemon option</li>
Windows: Fixed the issues which are related to start/stop Fluentd service</li>
</ul>

See Fluentd v1.16.7 has been released</a> blog article in details.</p>

Download</h2>

Please see the download page</a>.</p>

About next LTS schedule</h3>

We plan to ship the next LTS version of fluent-package v5.0.7 on June, 2025.
The content of updates are still in T.B.D.</p>

End of support for td-agent v4, let's migrate to fluent-package</h3>

As it was already announced Drop schedule announcement about EOL of Treasure Agent (td-agent) 4</a>, td-agent v4 reached EOL in Dec, 2023.</p>

After reached EOL, td-agent v4.5.3 on Windows was released because there was a crash bug during startup on Windows. It was backported fix from fluent-package v5 as
it is critical in some case. Even though this was a exceptional maintenance release, but there is no change to the fact that we already stopped maintaining td-agent v4.</p>

We strongly recommend migrating from td-agent v4 to fluent-package v5 (LTS).
See Upgrade to fluent-package v5</a></p>


Fluentd v1.16.7 has been released
2025-01-29
Hi users!</p>

We have released v1.16.7 on 2025-01-29.
ChangeLog is here</a>.</p>

This release is a maintenance release of v1.16 series.
In this release, some bugs which are related on Windows were fixed with backporting from v1.18.x.</p>

This release will be bundled for upcoming fluent-package</code> LTS version v5.0.6!</p>

Bug Fixes</h2>

Windows: Fix NoMethodError of --daemon option</h3>

In this release, we have fixed a bug that it will fail when --daemon</code> option is used on Windows.</p>

It was a regression bug since v1.16.0 on Windows, but usually running as a service is recommended way on Windows,
so most of Fluentd users were not affected.</p>

Windows: Fixed the issues which are related to start/stop Fluentd service</h3>

In this release, we have fixed the following bugs which are
related to start/stop the Fluentd service.</p>


Fixed an issue when stopping the service immediately after startup could leave the processes</li>
Fixed an issue where stopping service sometimes can not be completed forever</li>
</ul>

These bug were caused because stop event was not handled correctly in the previous releases.</p>

Typically, this bug will happen if you stop the Fluentd service immediately after startup.
Then it could leave the processes or stopping service sometimes can not be completed forever.</p>

Misc news</h2>

We also enforcing stabilizing CI of Fluentd.
It has nothing to do with Fluentd's functionality directly, but it is very important to provide stable version of Fluentd continuously.</p>

Not only Windows: Add workaround for unexpected exception #4747</a>,
many CI improvements was merged into master, then backported to v1.16 branch, too.</p>

Enjoy logging!</p>


fluent-package v5.2.0 has been released
2024-12-14
Hi users!</p>

We have released fluent-package v5.2.0</a>.
fluent-package is a stable distribution package of Fluentd. (successor of td-agent v4)</p>

This release is a new release of v5.2 series.</p>

Changes from fluent-package v5.1.0</h2>


Support upgrade fluentd service with zero-downtime</li>
Update ruby to 3.2.6</li>
Update bundled Fluentd to v1.18.0</li>
Update bundled gems overall</li>
Solved possibility of DoS through "NoMemoryError"</li>
msi: set GEM_HOME</code>/GEM_PATH</code> in fluentd.bat</li>
deb: suppress service restart by needrestart</li>
Fixed SIGABORT error with fluent-plugin-systemd</li>
</ul>

Support upgrade fluentd service with zero-downtime</h2>

Previously, when upgrading the fluent-package, you had to stop the fluentd service,
install the new version of the fluent-package, then install any necessary plugins,
and finally restart the fluentd service.</p>

Starting from fluent-package v5.2.0,
we have introduced the zero-downtime restart feature that automatically installs the required plugins during the upgrade process
and allows you to upgrade Fluentd without interrupting the logging service.</p>

Please refer to "Advisory for upgrading with zero-downtime".</p>

Solved possibility of DoS through "NoMemoryError"</h2>

In the previous versions of msgpack gem, there was a possibility that cause DoS (Denial Of Service)
when crafted message was sent to Fluentd.</p>

When that message was sent, it might cause "NoMemoryError" on Fluentd because there is a case that msgpack
try to pre-allocate huge amount of memories.</p>

Above behavior was fixed not to pre-allocate over 32k entries (limit pre-allocated amount of memories) in msgpack 1.7.3 and bundled.</p>

msi: set GEM_HOME</code>/GEM_PATH</code> in fluentd.bat</h2>

In the previous versions, fluentd.bat doesn't set GEMHOME/GEM</em>PATH explicitly.</p>

If users set custom GEM_HOME</code> / GEM_PATH</code> environment variables, the
batch file will not work as expected. Therefore, this patch will set
the appropriate values in the batch file.</p>

deb: suppress service restart by needrestart</h2>

We have changed so that Fluentd does not restart when the needrestart package is installed.
fluent-package v5.2.0 places /etc/needrestart/conf.d/50-fluent-package.conf</code>.</p>

Fixed SIGABORT error with fluent-plugin-systemd</h2>

In this release, the bundled fluent-plugin-systemd was updated to 1.1.0.
That release fixed SIGABORT error with inconsistency of memory allocator handling.</p>

Advisory for upgrading with zero-downtime</h2>

The zero-downtime restart feature can be configured by FLUENT_PACKAGE_SERVICE_RESTART</code> environment variable.
Please refer to following section for more details.</p>


Add FLUENT_PACKAGE_SERVICE_RESTART</code> environmental variable


This section explains FLUENT_PACKAGE_SERVICE_RESTART</code> environment variable.</li>
</ul></li>
Automate Plugin Install for Update on Demand


This section explains the mechanism that installs the plugins automatically during the upgrade process.</li>
</ul></li>
</ul>

Add FLUENT_PACKAGE_SERVICE_RESTART</code> environmental variable</h3>

We have introduced FLUENT_PACKAGE_SERVICE_RESTART</code> environment variable to configure the zero-downtime restart feature.
The variable exists in the following file:</p>


RPM: /etc/sysconfig/fluentd</code></li>
DEB: /etc/default/fluentd</code></li>
</ul>

Example:</p>

FLUENT_PACKAGE_OPTIONS=""
# Control method to upgrade service (auto/manual) restart
FLUENT_PACKAGE_SERVICE_RESTART=auto
</code></pre>

auto (default)</strong></h4>

The service automatically restarts with zero-downtime restart feature when all of the following conditions are met:</p>


The service was active before updating.</li>
The installed and upgrading versions are required 5.2.0 or higher (both sides must support this feature).</li>
</ol>

The plugins will be automatically reinstalled if needed if your environment has an active online connection.
For more details, please refer to "Automate Plugin Install for Update on Demand".</p>

manual</strong></h4>

You can use this approach if you prefer to manage plugins manually or if your environment does not have offline connection.
If the service was active before the update, it will not restart automatically with this configuration.
You need to restart the service manually.</p>


The zero-downtime restart:


Send a SIGUSR2</code> signal to the supervisor process, such as with kill -USR2 <PID></code></li>
</ul></li>
Normal restart:


Restart the service normally, such as with systemctl restart fluentd</code>.</li>
</ul></li>
</ul>

Automate Plugin Install for Update on Demand</h3>

Automate Plugin Management</h4>

If you prefer to manage plugins automatically, please set FLUENT_PACKAGE_SERVICE_RESTART</code> to auto</code> (default).</p>

When the service restarts automatically using the zero-downtime restart feature, any missing plugins are automatically detected and reinstalled before the restart.</p>

Previously, automatic restarts after updates were not recommended due to potential issues.
If you manually install plugins, you need to reinstall them before restarting when the embedded Ruby version is updated.</p>

To address this, this feature enables automatic plugin installation during the restart process. The steps are as follows:</p>


Collect the current list of plugins before the update.


Recognize gems as plugins that has fluent-plugin-</code> prefix.</li>
</ul></li>
After installing the updated package, detect missing plugins.


Compare the collected plugin list with the default plugins to identify any missing ones.</li>
</ul></li>
Install the missing plugins.</li>
</ol>

Manual Plugin Management</h4>

If you prefer to manage plugins manually, please set FLUENT_PACKAGE_SERVICE_RESTART</code> to manual</code>.
This is useful in cases such as:</p>


Pinning specific plugin versions</li>
Operating in an offline environment</li>
</ul>

In this mode, automatic plugin installation and restarts are disabled.
You can manually install plugins and send a SIGUSR2</code> signal to trigger the zero-downtime restart feature after the update.</p>

Caution: if you use a custom unit file, need to migrate it to use this feature safely</h3>

If you use a custom unit file, such as /etc/systemd/system/fluentd.service</code>, please remove these 2 lines.</p>

Environment=GEM_HOME=/opt/fluentd/lib/ruby/gems/...
Environment=GEM_PATH=/opt/fluentd/lib/ruby/gems/...
</code></pre>

We don't need GEM_HOME</code> and GEM_PATH</code>.
They will be removed after v5.2.0, but if you use a custom unit file, you need to remove them manually.
If these variables are set, the zero-downtime restart feature may not work correctly.
It is because the new process inherits the original environment variables if using this feature.</p>

Please refer to #713</a> for more details.</p>

Download</h2>

Please see the download page</a>.</p>

About next LTS schedule</h3>

We plan to ship the next LTS version of fluent-package v5.0.6 on March, 2025.
The content of updates are still in T.B.D.</p>

End of support for td-agent v4, let's migrate to fluent-package</h3>

As it was already announced Drop schedule announcement about EOL of Treasure Agent (td-agent) 4</a>, td-agent v4 was reached EOL in Dec, 2023.</p>

After reached EOL, td-agent v4.5.3 on Windows was released because there was a crash bug during startup on Windows. It was backported fix from fluent-package v5 as
it is critical in some case. Even though this was a exceptional maintenance release, but there is no change to the fact that we already stopped maintaining td-agent v4.</p>

We strongly recommend migrating from td-agent v4 to fluent-package v5 (LTS).
See Upgrade to fluent-package v5</a></p>


Fluentd v1.18.0 has been released
2024-11-29
Hi users!</p>

We have released v1.18.0 on 2024-11-29. ChangeLog is here</a>.</p>

This release is a new release of v1.18 series.
In this release, we added zero-downtime-restart as a key feature, enhanced some features and fixed bugs.</p>

Enhancement</h2>

Add zero-downtime-restart feature</h3>

In this release, we have added the feature to update the Fluentd process with zero downtime for Linux and macOS environments (not supported on Windows).
You can use this feature to reload config and restart Fluentd gracefully.</p>

You can use this feature by sending a SIGUSR2</code> signal to the supervisor process,
and this changes behavior SIGUSR2</code> from graceful reload to zero-downtime-restart feature on Linux and macOS environments.</p>

You can still use the conventional graceful reloading feature by directly sending SIGUSR2</code> to each worker process or using the RPC feature.
However, it had some limitations and issues (Please see #4624</a> for details).
So, we recommend using this new feature for graceful reloading/restarting unless there is a particular reason.</p>

Please see #4624</a> for more information.</p>

Add with-source-only feature</h3>

This feature has been added to support the zero-downtime-restart feature that it launches Fluentd with input plugins only.</p>

This feature has added --with-source-only</code> option in fluentd</code> command, with_source_only</code> option in system configuration and out_buffer</code> plugin which can be used for buffering and relabeling events.
These are used internally to support zero-downtime-restart.</p>

Please see #4661</a> for more information.</p>

Config File Syntax: Extend Embedded Ruby Code support for Hashes and Arrays</h3>

The Embedded Ruby Code</a> has been supported in configuration.
In this release, we have extended the syntax to allow the use of Embedded Ruby Code in Hashes and Arrays.</p>

Example:</p>

key1 ["foo","#{1 + 1}"] # Embedded Ruby Code in Array syntax
key2 {"foo":"#{1 + 1}"} # Embedded Ruby Code in Hash syntax
</code></pre>

Result:</p>

key1 ["foo","2"]
key2 {"foo":"2"}
</code></pre>

Please note that this is not backward compatible, although we assume that this will never affect to actual existing configs.</p>

In case the behavior changes unintentionally, you can disable this feature by surrounding the entire value with single quotes.</p>

Example:</p>

key '{"foo":"#{1 + 1}"}'
</code></pre>

transport tls: Use SSL_VERIFY_NONE</code> by default</h3>

We have changed the flags to SSL_VERIFY_NONE</code> by default for server the certification verification.</p>

In the previous versions, it had been necessary to set client_cert_auth false</code> and insecure true</code> to apply SSLVERIFY</em>NONE.
This was an inappropriate combination of settings.
In this release, it can make it possible to apply SSL_VERIFY_NONE</code> with just client_cert_auth false</code> (default).</p>

transport tls: Add ensure_fips</code> option to ensure FIPS compliant mode</h3>

We have added ensure_fips</code> option in transport</code> section in config to check FIPS mode.
When it configures ensure_fips true</code>, it will check FIPS mode is supported in your environment, if not, just aborts.
By default, it has disabled.</p>

Example:</p>

<transport tls>
  ensure_fips true
</transport>
</code></pre>

Please see the document</a> for more information.</p>

plugin_helper/server: Add receive_buffer_size</code> parameter in transport section</h3>

In the previous versions, the receive_buffer_size</code> option can be set by in_udp</code> only.
In this release, we have added the receive_buffer_size</code> option into transport</code> section too to configure the buffer size on in_tcp</code> or in_syslog</code> plugins.</p>

Example:</p>

<transport udp>
  receive_buffer_size 4194304
</transport>
</code></pre>

filter_parser: Now able to handle multiple parsed results</h3>

In the previous versions, there was a restriction that only the first record could be handled when the parsed result was multiple records.
In this release, we have removed this limitation to handle multiple records appropriately.</p>

You can read more about this limitation in the Remaining problem: filter_parser</a> in Fluentd v1.17.0 release blog.</p>

in_http: add add_tag_prefix</code> option</h3>

We have added add_tag_prefix</code> option in in_http</code> plugin to add the prefix to the incoming event's tag, similar to in_forward</code> plugin.</p>

Example:</p>

<source>
  @type http
  add_tag_prefix prod
</source>
</code></pre>

System configuration: add path option in log section</h3>

We have added path</code> option to log</code> section of system configuration.</p>

Example:</p>

<system>
  <log>
    path /path/to/log_file
  </log>
</system>
</code></pre>

Bug Fix</h2>

command: fix NoMethodError of --daemon under Windows</h3>

We have fixed a NoMethodError when launches fluentd</code> with --daemon</code> command line option under Windows platform.</p>

fluentd command: fix --plugin (-p) option not to overwrite default value</h3>

We have fixed --plugin</code> command line option that it does not overwrite the default value.</p>

Enjoy logging!</p>


fluent-package v5.0.5 has been released
2024-11-08
Hi users!</p>

We have released fluent-package v5.0.5</a>.
fluent-package is a stable distribution package of Fluentd. (successor of td-agent v4)</p>

This is a maintenance release of v5.0.x LTS series.
As bundled Ruby was updated to 3.2.6 and Fluentd was updated to 1.16.6.
We recommend upgrading to fluent-package v5.0.5!</p>

Changes from fluent-package v5.0.4</h3>

In this release, focused on updating bundled ones.</p>


Update ruby to 3.2.6</li>
Update fluentd to 1.16.6</li>
Update bundled gems overall</li>
Solved possibility of DoS through "NoMemoryError"</li>
msi: set GEM_HOME</code>/GEM_PATH</code> in fluentd.bat</li>
Fixed SIGABORT error with fluent-plugin-systemd</li>
</ul>

Solved possibility of DoS through "NoMemoryError"</h3>

In the previous versions of msgpack gem, there was a possibility that cause DoS (Denial Of Service)
when crafted message was sent to Fluentd.</p>

When that message was sent, it might cause "NoMemoryError" on Fluentd because there is a case that msgpack
try to pre-allocate huge amount of memories.</p>

Above behavior was fixed not to pre-allocate over 32k entries (limit pre-allocated amount of memories) in msgpack 1.7.3 and bundled into fluent-package v5.0.5.</p>

msi: set GEM_HOME</code>/GEM_PATH</code> in fluentd.bat</h3>

In the previous versions, fluentd.bat doesn't set GEMHOME/GEM</em>PATH explicitly.</p>

If users set custom GEM_HOME</code> / GEM_PATH</code> environment variables, the
batch file will not work as expected. Therefore, this patch will set
the appropriate values in the batch file.</p>

Above bug was also fixed in fluent-package v5.0.5.</p>

Fixed SIGABORT error with fluent-plugin-systemd</h3>

In this release, the bundled fluent-plugin-systemd was updated to 1.1.0.
That release fixed SIGABORT error with inconsistency of memory allocator handling.</p>

Download</h3>

Please see the download page</a>.</p>

About next LTS schedule</h4>

We plan to ship the next LTS version of fluent-package v5.0.6 on March, 2025.
The content of updates are still in T.B.D.</p>

End of support for td-agent v4, let's migrate to fluent-package</h4>

As it was already announced Drop schedule announcement about EOL of Treasure Agent (td-agent) 4</a>, td-agent v4 was reached EOL in Dec, 2023.</p>

After reached EOL, td-agent v4.5.3 on Windows was released because there was a crash bug during startup on Windows. It was backported fix from fluent-package v5 as
it is critical in some case. Even though this was a exceptional maintenance release, but there is no change to the fact that we already stopped maintaining td-agent v4.</p>

We strongly recommend migrating from td-agent v4 to fluent-package v5 (LTS).
See Upgrade to fluent-package v5</a></p>


Scheduled support lifecycle announcement about Fluent Package v6
2024-08-29
Hi users!</p>

We had launched fluent-package</code> v5 series last year, recently shipped v5.0.4</a> in LTS release channel and
v5.1.0</a> in normal release channel.</p>

In this blog article, we explains the planned next major updates - v6.0.0.</p>

When the next LTS (Long Term Support) version available?</h3>

In short, we will ship fluent-package v6 in Aug, 2025.</p>

We keeps two release channels as follows:</p>


Normal release</li>
LTS (Long Term Support)</li>
</ul>

Here is the difference of these channels.</p>


Normal release (6.x series)


Recommended for early adopters (eager to try new features of Fluentd)</li>
Rapid release development (planned semi-annually releases, but it may vary.)</li>
Fluentd will be upgraded occasionally


Minor upgrade will be applied. e.g. 1.18 => 1.19 and so on.</li>
e.g. v6.0.1 (Fluentd v1.18.1), v6.0.2 (Fluentd v1.18.2), ... v6.1.0 (Fluentd v1.19.0)</li>
</ul></li>
The only latest version will be supported (bug fix will not be backported into older version)</li>
</ul></li>
LTS (Long Term Support, 6.0.x series)


Recommended for enterprise services</li>
Security and bug fix release only</li>
Fluentd will be upgraded only in the teeny version and will stick to 1.18.x series. (T.B.D.)


Thus, the version number will be 6.0.x. (6.1 series will not be shipped for LTS channel)</li>
e.g. v6.0.1 (Fluentd v1.18.1), v6.0.2 (Fluentd v1.18.2), v6.0.3 (Fluentd v1.18.3) ... v6.0.x (Fluentd v1.18.x) and so on.</li>
</ul></li>
Next major version will be fluent-package</code> v7.0.0, and will be shipped in 2027 (T.B.D.).</li>
</ul></li>
</ul>

As for fluent-package v6,</p>


fluent-package v5 LTS will be supported until Dec, 2025.


We expect users upgrade from v5 to v6 during the grace period.</li>
</ul></li>
Until 6.1.0 is released, normal release channel and LTS channel are the same package.</li>
Upgrade from v4 or older version is not supported. Upgrade to v5 first, then upgrade it to v6.</li>
</ul>

Current releases and future plans:</p>

</p>





Release Version</th>
Release Date</th>
End of life</th>
</tr>

v5.0.x (LTS)</td>
Aug, 2023</td>
Dec, 2025</td>
</tr>

v6.0.0 (LTS)</td>
Aug, 2025</td>
Dec, 2027 (T.B.D.)</td>
</tr>

v7.0.0 (LTS)</td>
Aug, 2027 (T.B.D.)</td>
T.B.D.</td>
</tr>
</table>

Happy logging!</p>


Fluentd v1.16.6 has been released
2024-08-20
Hi users!</p>

We have released v1.16.6 on 2024-08-20. ChangeLog is here</a>.</p>

This release is a maintenance release of v1.16 series.
In this release, some bugs were fixed with backporting from v1.17.x.</p>

Bug Fixes</h2>

yaml_parser</code>: $log_level</code> notation in YAML was supported</h3>

In this release, we added a support for $log_level</code> in YAML config file syntax</a>.</p>

In the previous versions, if you used log_level</code> in YAML configuration, it causes a following warning:</p>

[warn]: #0 'log_level' is deprecated parameter name. use '@log_level' instead.
</code></pre>

But @log_level</code> is invalid in YAML format. In YAML format, it should be $log_level</code> as same as 
similar parameter such as $tag</code> and $type</code>, but not supported before.</p>

Since Fluentd v1.16.6, $log_level</code> has been supported! (In v1.17.x, it was supported since v1.17.1)</p>

fluentd command: Fix --plugin</code> (-p) option not to overwrite default value</h3>

In this release, we have fixed a bug that fluentd command: --plugin</code> (-p) option could not overwrite default value.</p>

This bug was unexpectedly introduced since v1.16.0.</p>

Now it was reverted to the original behavior.</p>

logger: Fix LoadError with console gem v1.25</h3>

In this release, we fixed a LoadError with console gem v1.25 or later.</p>

Since console gem v1.25 or later, it's internal change causes a LoadError in Fluentd.
This error breaks existing plugin such as fluent-plugin-prometheus which provides monitoring REST API.</p>


500 response when scraping prometheus metrics in kubernetes with istio service mesh</a></li>
</ul>

With supporting console gem v1.25 or later, this issue has solved!</p>

Enjoy logging!</p>


Fluentd v1.17.1 has been released
2024-08-19
Hi users!</p>

We have released v1.17.1 on 2024-08-19. ChangeLog is here</a>.</p>

This release is a new release of v1.17 series.
In this release, we added some new options for some plugins and fixed bugs of Parser.</p>

Enhancement</h2>

yaml_parser</code>: $log_level</code> notation in YAML was supported</h3>

In this release, we added a support for $log_level</code> in YAML config file syntax</a>.</p>

In the previous versions, if you used log_level</code> in YAML configuration, it causes a following warning:</p>

[warn]: #0 'log_level' is deprecated parameter name. use '@log_level' instead.
</code></pre>

But @log_level</code> is invalid in YAML format. In YAML format, it should be $log_level</code> as same as 
similar parameter such as $tag</code> and $type</code>, but not supported before.</p>

Since Fluentd v1.17.1, $log_level</code> has been supported now!</p>

out_http</code>: compress</code> option was supported</h3>

In this release, we added a new option compress</a> for the out_http</a> plugin.</p>

You can compress HTTP request body by specifying compress gzip</code>.
To keep compatibility, the default configuration is set as compress text</code> (no compression).</p>

This feature was contributed by @rockliffelewis. Thanks!</p>

in_sample</code>: the default behavior was changed</h3>

In this release, we changed the default behavior of in_sample</a> plugin and added a new option reuse_record</a> for it.</p>

The default behavior has changed to copy sample data to avoid the impact of destructive changes by subsequent plugins.</p>

In the previous versions, when in_sample</code> plugin is used with the subsequent filter parser plugin which uses remove_key_name_field</code>, it raises the following error repeatedly.</p>

#0 dump an error event: error_class=ArgumentError error="message does not exist"
</code></pre>

This error occurs when key_name</code> and remove_key_name_field</code> removes key from record with destructive change in filter parser.
It affects generated sample data after twice or later.
(This error is not limited to filter parser plugin. The similar destructive change will be done with the subsequent plugins, this error is reproducible)</p>

The new default behavior (reuse_record false</code>) avoids this problem, but it increases the load when generating large amounts of sample data.
You can use this new parameter to have the same performance as before with reuse_record</code>.</p>

Bug Fixes</h2>

logger: Fix LoadError with console gem v1.25</h3>

In this release, we fixed a LoadError with console gem v1.25 or later.</p>

Since console gem v1.25 or later, it's internal change causes a LoadError in Fluentd.
This error breaks existing plugin such as fluent-plugin-prometheus which provides monitoring REST API.</p>


500 response when scraping prometheus metrics in kubernetes with istio service mesh</a></li>
</ul>

With supporting console gem v1.25 or later, this issue has solved!</p>

Enjoy logging!</p>


fluent-package v5.1.0 has been released
2024-08-02
Hi users!</p>

We have released fluent-package v5.1.0</a>.
fluent-package is a stable distribution package of Fluentd. (successor of td-agent v4)</p>

This release is a new release of v5.1 series.
Bundled ruby version was upgraded to 3.2.5 and fluentd v1.17.0 was shipped!</p>

Changes from fluent-package v5.0.4</h3>

In this release, focused on updating bundled ones.</p>


Update fluentd to 1.17.0</li>
Update ruby to 3.2.5</li>
Update bundled gems overall</li>
</ul>

Update bundled components overall</h3>

In LTS version, conservative updating policy is enabled, so updating gem is very limited to bug fix or security fix.
In contrast to LTS version, v5.1.0 bundles more recent components because of standard version.</p>

As we already announced in Scheduled support lifecycle announcement about Fluent Package</a>
blog article, in normal release channel, we will ship the latest version (v1.17.0) of Fluentd.</p>

So if you want to try using latest version of Fluentd, v5.1.0 is one for you.
If you use fluent-package in enterprise services, keep using fluent-package 5.0.x (LTS).</p>


</i>
Note:</b>In the previous versions, there is no different in normal release channel and LTS release channel. But 
from this release, v5.1.x will be shipped in normal release channel. v5.0.x will be shipped in LTS channel.
</div>

Download</h3>

Please see the download page</a>.</p>

About next LTS schedule</h4>

We plan to ship the next LTS version of fluent-package v5.0.5 on Oct, 2024.
The content of updates are still in T.B.D.</p>

End of support for td-agent v4, let's migrate to fluent-package</h4>

As it was already announced Drop schedule announcement about EOL of Treasure Agent (td-agent) 4</a>, td-agent v4 was reached EOL in Dec, 2023.</p>

After reached EOL, td-agent v4.5.3 on Windows was released because there was a crash bug during startup on Windows. It was backported fix from fluent-package v5 as
it is critical in some case. Even though this was a exceptional maintenance release, but there is no change to the fact that we already stopped maintaining td-agent v4.</p>

We strongly recommend migrating from td-agent v4 to fluent-package v5 (LTS).
See Upgrade to fluent-package v5</a></p>

Automate Plugin Install for Update on Demand</h3>

Bug Fix</h2>

command: fix NoMethodError of --daemon under Windows</h3>
We have fixed a NoMethodError when launches `fluentd</code> with --daemon</code> command line option under Windows platform.</p>`

`fluentd command: fix --plugin (-p) option not to overwrite default value</h3> We have fixed --plugin</code> command line option that it does not overwrite the default value.</p> Enjoy logging!</p>`

Download</h3>
Please see the download page</a>.</p>

Fluentd v1.16.6 has been released

Fluentd v1.17.1 has been released

fluent-package v5.1.0 has been released

Download</h3>
Please see the download page</a>.</p>

Fluentd Blog

Drop Alpine and switch default to Debian for Fluentd docker image

fluent-package v5.0.6 has been released

Fluentd v1.16.7 has been released

fluent-package v5.2.0 has been released

Fluentd v1.18.0 has been released

fluent-package v5.0.5 has been released

Scheduled support lifecycle announcement about Fluent Package v6

Fluentd Blog

Drop Alpine and switch default to Debian for Fluentd docker image

fluent-package v5.0.6 has been released

Changes from fluent-package v5.0.5</h2> In this release, known Windows issues were fixed.</p> Update bundled Fluentd to v1.16.7</li> Update bundled gems overall</li>

Fluentd v1.16.7 has been released

Windows: Fixed the issues which are related to start/stop Fluentd service</h3> In this release, we have fixed the following bugs which are related to start/stop the Fluentd service.</p> Fixed an issue when stopping the service immediately after startup could leave the processes</li>

Misc news</h2> We also enforcing stabilizing CI of Fluentd. It has nothing to do with Fluentd's functionality directly, but it is very important to provide stable version of Fluentd continuously.</p>

fluent-package v5.2.0 has been released

Advisory for upgrading with zero-downtime</h2> The zero-downtime restart feature can be configured by FLUENT_PACKAGE_SERVICE_RESTART</code> environment variable. Please refer to following section for more details.</p>

Automate Plugin Install for Update on Demand</h3>

Fluentd v1.18.0 has been released

filter_parser: Now able to handle multiple parsed results</h3> In the previous versions, there was a restriction that only the first record could be handled when the parsed result was multiple records. In this release, we have removed this limitation to handle multiple records appropriately.</p>

Bug Fix</h2>

command: fix NoMethodError of --daemon under Windows</h3> We have fixed a NoMethodError when launches fluentd</code> with --daemon</code> command line option under Windows platform.</p>

fluentd command: fix --plugin (-p) option not to overwrite default value</h3> We have fixed --plugin</code> command line option that it does not overwrite the default value.</p> Enjoy logging!</p>

fluent-package v5.0.5 has been released

Changes from fluent-package v5.0.4</h3> In this release, focused on updating bundled ones.</p> Update ruby to 3.2.6</li> Update fluentd to 1.16.6</li> Update bundled gems overall</li> Solved possibility of DoS through "NoMemoryError"</li> msi: set GEM_HOME</code>/GEM_PATH</code> in fluentd.bat</li>

Scheduled support lifecycle announcement about Fluent Package v6

Fluentd v1.16.6 has been released

Fluentd v1.17.1 has been released

fluent-package v5.1.0 has been released

command: fix NoMethodError of --daemon under Windows</h3>
We have fixed a NoMethodError when launches `fluentd</code> with --daemon</code> command line option under Windows platform.</p>`

`fluentd command: fix --plugin (-p) option not to overwrite default value</h3> We have fixed --plugin</code> command line option that it does not overwrite the default value.</p> Enjoy logging!</p>`