Scheduled support lifecycle announcement about Fluent Package v6

Hi users!

We had launched fluent-package v5 series last year, recently shipped v5.0.4 in LTS release channel and v5.1.0 in normal release channel.

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

When the next LTS (Long Term Support) version available?

In short, we will ship fluent-package v6 in Aug, 2025.

We keeps two release channels as follows:

  • Normal release
  • LTS (Long Term Support)

Here is the difference of these channels.

  • Normal release (6.x series)
    • Recommended for early adopters (eager to try new features of Fluentd)
    • Rapid release development (planned semi-annually releases, but it may vary.)
    • Fluentd will be upgraded occasionally
      • Minor upgrade will be applied. e.g. 1.18 => 1.19 and so on.
      • e.g. v6.0.1 (Fluentd v1.18.1), v6.0.2 (Fluentd v1.18.2), ... v6.1.0 (Fluentd v1.19.0)
    • The only latest version will be supported (bug fix will not be backported into older version)
  • LTS (Long Term Support, 6.0.x series)
    • Recommended for enterprise services
    • Security and bug fix release only
    • 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)
      • 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.
    • Next major version will be fluent-package v7.0.0, and will be shipped in 2027 (T.B.D.).

As for fluent-package v6,

  • fluent-package v5 LTS will be supported until Dec, 2025.
    • We expect users upgrade from v5 to v6 during the grace period.
  • Until 6.1.0 is released, normal release channel and LTS channel are the same package.
  • Upgrade from v4 or older version is not supported. Upgrade to v5 first, then upgrade it to v6.

Current releases and future plans:

Release Version Release Date End of life
v5.0.x (LTS) Aug, 2023 Dec, 2025
v6.0.0 (LTS) Aug, 2025 Dec, 2027 (T.B.D.)
v7.0.0 (LTS) Aug, 2027 (T.B.D.) T.B.D.

Happy logging!

Read More

Fluentd v1.16.6 has been released

Hi users!

We have released v1.16.6 on 2024-08-20. ChangeLog is here.

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

Bug Fixes

yaml_parser: $log_level notation in YAML was supported

In this release, we added a support for $log_level in YAML config file syntax.

In the previous versions, if you used log_level in YAML configuration, it causes a following warning:

[warn]: #0 'log_level' is deprecated parameter name. use '@log_level' instead.

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

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

fluentd command: Fix --plugin (-p) option not to overwrite default value

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

This bug was unexpectedly introduced since v1.16.0.

Now it was reverted to the original behavior.

logger: Fix LoadError with console gem v1.25

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

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.

With supporting console gem v1.25 or later, this issue has solved!

Enjoy logging!

Read More

Fluentd v1.17.1 has been released

Hi users!

We have released v1.17.1 on 2024-08-19. ChangeLog is here.

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.

Enhancement

yaml_parser: $log_level notation in YAML was supported

In this release, we added a support for $log_level in YAML config file syntax.

In the previous versions, if you used log_level in YAML configuration, it causes a following warning:

[warn]: #0 'log_level' is deprecated parameter name. use '@log_level' instead.

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

Since Fluentd v1.17.1, $log_level has been supported now!

out_http: compress option was supported

In this release, we added a new option compress for the out_http plugin.

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

This feature was contributed by @rockliffelewis. Thanks!

in_sample: the default behavior was changed

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

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

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

#0 dump an error event: error_class=ArgumentError error="message does not exist"

This error occurs when key_name and remove_key_name_field 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)

The new default behavior (reuse_record false) 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.

Bug Fixes

logger: Fix LoadError with console gem v1.25

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

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.

With supporting console gem v1.25 or later, this issue has solved!

Enjoy logging!

Read More

fluent-package v5.1.0 has been released

Hi users!

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

This is a maintenance release of v5.x series. Bundled ruby version was upgraded to 3.2.5 and fluentd v1.17.0 was shipped!

Changes from fluent-package v5.0.4

In this release, focused on updating bundled ones.

  • Update fluentd to 1.17.0
  • Update ruby to 3.2.5
  • Update bundled gems overall

Update bundled components overall

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.

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

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).

Download

Please see the download page.

About next LTS schedule

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.

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

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

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.

We strongly recommend migrating from td-agent v4 to fluent-package v5 (LTS). See Upgrade to fluent-package v5

Read More

fluent-package v5.0.4 has been released

Hi users!

We have released fluent-package v5.0.4. fluent-package is a stable distribution package of Fluentd. (successor of td-agent v4)

This is a maintenance release of v5.0.x LTS series. As bundled Ruby was updated to 3.2.4 and a foolproof mechanism was implemented to prevent launching duplicated Fluentd instances, we recommend upgrading to fluent-package v5.0.4!

Changes from fluent-package v5.0.3

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

Fixed to prevent launching Fluentd wrongly if the service is already running

In this release, a foolproof mechanism was implemented to prevent launching Fluentd wrongly if the service is already running.

As you know, you can check the version of Fluentd with fluentd --version, but there is a case that fluentd -v is executed wrongly to do it.

When already running Fluentd as a service, fluentd -v launches a duplicated Fluentd instance with the same fluentd configuration. If you launch duplicated Fluentd instances, it causes the corruption of processing Fluentd buffer. To prevent such a situation, a foolproof was implemented now.

For example, if Fluentd is running as a service, launching Fluentd causes an error to block it.

Here is the example on Windows:

> fluentd
Error: Can't start duplicate Fluentd instance with the default config.

To start Fluentd, please do one of the following:
  (Caution: Please be careful not to start multiple instances with the same config.)
  - Stop the Fluentd Windows service 'fluentdwinsvc'.
  - Specify the config path explicitly by '-c' ('--config').

Even though if you wrongly launch Fluentd to check version with -v (It should be --version to show version), then it causes the following error.

> fluentd -v
Error: Can't start duplicate Fluentd instance with the default config.

To take the version, please use '--version', not '-v' ('--verbose').

To start Fluentd, please do one of the following:
  (Caution: Please be careful not to start multiple instances with the same config.)
  - Stop the Fluentd Windows service 'fluentdwinsvc'.
  - Specify the config path explicitly by '-c' ('--config')

Note that this foolproof feature is intended to block launching duplicated Fluentd instance, you can explicitly launch Fluentd by specifying a specific option to pass it even though already Fluentd is running as a service.

On Windows:

  • -c (--config)
  • --dry-run
  • --reg-winsvc
  • --reg-winsvc-fluentdopt
  • --show-plugin-config

On Linux:

  • -c (--config)
  • --dry-run
  • --show-plugin-config

About next LTS schedule

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.

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

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

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.

We strongly recommend migrating from td-agent v4 to fluent-package v5 (LTS). See Upgrade to fluent-package v5

Download

Please see the download page.

Read More