Release Version</th>	Release Date</th>	End of life</th> </tr>
v4.5.1</td>	Aug, 2023</td>	Dec, 2023</td> </tr>
v5.0.1 (LTS)</td>	Aug 29, 2023</td>	March, 2025</td> </tr>
v6.0.0 (LTS)</td>	March, 2025? (T.B.D.)</td>	T.B.D.</td> </tr> </table> Happy logging!</p>

Fluentd v1.17.0 has been released

2024-04-30

Hi users!</p>

We have released v1.17.0 on 2024-04-30. ChangeLog is here</a>.</p>

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

Enhancement</h2>

in_tail</code>: Add glob_policy</code> option for expanding glob capability of path</code> and exclude_path</code></h3>

In this release, we added a new option glob_policy</a> for in_tail</a> plugin.</p>

In previous versions, we can use only *</code> in glob patterns for path</a> and exclude_path</a> option.</p>

Example:</p>

path /path/to/*
exclude_path ["/path/to/*.gz", "/path/to/*.zip"]
</code></pre>

From this version, we can also use []</code>, ?</code>, and {}</code> in glob patterns depending on the glob_policy</code> option.</p>

Example:</p>

path "[0-1][2-3].log"
glob_policy extended
</code></pre>

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

out_http</code>: Support AWS Signature Version 4 authentication</h3>

In this release, we added a new option aws_sigv4</code> for the method</a> setting of out_http</a> plugin.</p>

By using this option, out_http</code> can use AWS Signature Version 4</a>.</p>

For example, this allows out_http</code> to write to Amazon OpenSearch Ingestion</a>.</p>

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

out_http</code>: Add option to reuse connections</h3>

In this release, we add a new option reuse_connections</a> for out_http</a> plugin.</p>

This option will improve throughput of out_http</code>.</p>

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

in_http</code>: Recognize CSP reports as JSON data</h3>

In this release, we make the data type of the request where the Content-Type</code> is application/csp-report</code> be considered JSON by default.</p>

Now, in_http</code> can receive Content Security Policy</a>'s report by default.</p>

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

Bug Fixes</h2>

Make sure parser returns hash</h3>

The record data in an event of Fluentd must be a hash object.</p>


Life of a Fluentd event</a></li>
</ul>

However, in the previous versions, some parser plugins could return a non-hash object, such as an array.
It could cause errors in subsequent processing.</p>

In this release, the following parser plugins have been fixed.</p>


parser_json</a></li>
parser_msgpack</a></li>
</ul>

The changes are as follows:</p>


Make sure to return a hash record.</li>
Make sure to accept only a hash or an array of hash.</li>
</ul>

Here are the details for each case.</p>

Example of changed behavior</h4>

Config:</p>

<source>
  @type tcp
  tag test.tcp
  <parse>
    @type json
  </parse>
</source>

<match test.**>
  @type stdout
</match>
</code></pre>

Send an array data:</p>

$ netcat 0.0.0.0 5170
[{"k":"v"}, {"k2":"v2"}]
</code></pre>

The result before this version:</p>

{datetime} test.tcp: [{"k":"v"},{"k2":"v2"}]
</code></pre>

The result after this version:</p>

{datetime} test.tcp: {"k":"v"}
{datetime} test.tcp: {"k2":"v2"}
</code></pre>

Example of resolved error</h4>

Config:</p>

<source>
  @type tcp
  tag test.tcp
  <parse>
    @type json
    null_empty_string
  </parse>
</source>

<match test.**>
  @type stdout
</match>
</code></pre>

Send an array data:</p>

$ netcat 0.0.0.0 5170
[{"k":"v"}, {"k2":"v2"}]
</code></pre>

The result before this version:</p>

{datetime} [error]: #0 unexpected error on reading data host="xxx" port=xxx error_class=NoMethodError error="undefined method `each_key' for [{\"k\"=>\"v\"}, {\"k2\"=>\"v2\"}]:Array"
</code></pre>

The result after this version:</p>

{datetime} test.tcp: {"k":"v"}
{datetime} test.tcp: {"k2":"v2"}
</code></pre>

Remaining problem: filter_parser</h4>

In the previous versions, filter_parser</code> could return an array record based on this wrong behavior.
From this release, it can not return multiple parsed results anymore and Fluentd outputs a warning log in this case.
This behavior should improve in the future.</p>

Here is an example.</p>

<source>
  @type sample
  tag test.array
  sample {"message": "[{\"k\":\"v\"}, {\"k2\":\"v2\"}]"}
</source>

<filter test.**>
  @type parser
  key_name message
  <parse>
    @type json
  </parse>
</filter>

<match test.**>
  @type stdout
</match>
</code></pre>

The result before this version:</p>

{datetime} test.array: [{"k":"v"},{"k2":"v2"}]
</code></pre>

The result after this version:</p>

{datetime} [warn]: #0 dump an error event: error_class=Fluent::Plugin::Parser::ParserError error="Could not emit the event. The parser returned multiple results, but currently filter_parser plugin only returns the first parsed result. Raw data: '[{\"k\":\"v\"}, {\"k2\":\"v2\"}]'" location=nil tag="test.array" time=xxx record={"k2"=>"v2"}
{datetime} test.array: {"k":"v"}
</code></pre>

These are the major changes for this release.</p>

In addition, some performance improvements have been included!
Please see ChangeLog</a> for details!</p>

Enjoy logging!</p>

About next LTS schedule</h3>
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>

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

About next LTS schedule</h3>
We plan to ship next LTS version of fluent-package v5.0.4 on June, 2024. The content of updates are still in T.B.D.</p>

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

About next LTS schedule</h3>
We plan to ship next LTS version of fluent-package v5.0.3 on Feb, 2024. The content of updates are still in T.B.D.</p>

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

How to migrate to Fluent Package v5</h2>
There is a good article to do it.</p>

Upgrade to fluent-package v5</a></li> </ul>
Follow the above instructions.</p>

Fluentd Blog

fluent-package v5.0.4 has been released

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

Update ruby to 3.2.4 (#645</a>)</li>
Fixed to prevent launching Fluentd wrongly if the service is already running (#648</a>,#649</a>)</li>
Added support for Ubuntu 24.04 (Noble Numbat)</li> </ul>

Fluentd v1.17.0 has been released

fluent-package v5.0.3 has been released

Fluentd v1.16.5 has been released

Fluentd v1.16.4 has been released

Open Source Summit Japan 2023

fluent-package v5.0.2 has been released

Fluentd v1.16.3 and v1.16.2 have been released

Drop schedule announcement about EOL of Treasure Agent (td-agent) 4

About Treasure Agent (td-agent) 4</h2>
Since td-agent 4.0.0 was released in 2020, td-agent 4 has been maintained for a long time.</p>
As new major version of td-agent 4 was rebranded (to `fluent-package</code> v5), and released in August 2023, we decided to stop maintaining td-agent 4.</p>`

Scheduled support lifecycle announcement about Fluent Package

Fluentd Blog

fluent-package v5.0.4 has been released

About next LTS schedule</h3> 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>

Fluentd v1.17.0 has been released

Bug Fixes</h2> Make sure parser returns hash</h3> The record data in an event of Fluentd must be a hash object.</p>

Make sure parser returns hash</h3> The record data in an event of Fluentd must be a hash object.</p>

Example of changed behavior</h4> Config:</p>

fluent-package v5.0.3 has been released

About next LTS schedule</h3> We plan to ship next LTS version of fluent-package v5.0.4 on June, 2024. The content of updates are still in T.B.D.</p>

Fluentd v1.16.5 has been released

Fluentd v1.16.4 has been released

Others</h3> in_tail</code>: Fix tail watchers in rotate_wait</code> state not being managed. #4334</a> This problem should not have any actual negative impact on the operation.</li> </ul></li>

Open Source Summit Japan 2023

fluent-package v5.0.2 has been released

About next LTS schedule</h3> We plan to ship next LTS version of fluent-package v5.0.3 on Feb, 2024. The content of updates are still in T.B.D.</p>

Fluentd v1.16.3 and v1.16.2 have been released

Drop schedule announcement about EOL of Treasure Agent (td-agent) 4

About Treasure Agent (td-agent) 4</h2> Since td-agent 4.0.0 was released in 2020, td-agent 4 has been maintained for a long time.</p> As new major version of td-agent 4 was rebranded (to fluent-package</code> v5), and released in August 2023, we decided to stop maintaining td-agent 4.</p>

How to migrate to Fluent Package v5</h2> There is a good article to do it.</p>

Scheduled support lifecycle announcement about Fluent Package

About next LTS schedule</h3>
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>

About next LTS schedule</h3>
We plan to ship next LTS version of fluent-package v5.0.4 on June, 2024. The content of updates are still in T.B.D.</p>

About next LTS schedule</h3>
We plan to ship next LTS version of fluent-package v5.0.3 on Feb, 2024. The content of updates are still in T.B.D.</p>

About Treasure Agent (td-agent) 4</h2>
Since td-agent 4.0.0 was released in 2020, td-agent 4 has been maintained for a long time.</p>
As new major version of td-agent 4 was rebranded (to `fluent-package</code> v5), and released in August 2023, we decided to stop maintaining td-agent 4.</p>`

How to migrate to Fluent Package v5</h2>
There is a good article to do it.</p>

Upgrade to fluent-package v5</a></li> </ul>
Follow the above instructions.</p>