Upgrade Guide for fluent-package v6

On August 29, 2025, we released fluent-package v6 as a new series of stable packages.

What is Fluent Package v6 LTS?

Fluent Package v6 LTS is a long-term support (LTS), stable package of Fluentd.

Fluent Package v5 LTS will reach end of support at the end of 2025. As its successor, Fluent Package v6 LTS will be supported until at least the end of 2027.

For more details, see the following article:

Upgrade procedure to Fluent Package v6 LTS

As an example, you can upgrade with the following steps:

  1. Check manually installed plugins
  2. Stop the Fluentd service
  3. Back up registry settings (Windows only)
  4. Install Fluent Package v6 LTS
  5. Reinstall plugins
  6. Restart the Fluentd service

Below are details for each step.

1. Check manually installed plugins

If your current version (before upgrade) is Fluent Package v5.0.2 or later (v5.0.3 for Windows), you can use the bundled fluent-diagtool to list manually installed plugins.

Run the following command:

$ /opt/fluent/bin/fluent-diagtool -t fluentd -o /tmp
  • -t fluentd: required
  • -o /tmp: specifies the output directory for results (you can choose any directory)

The tool outputs various information to standard output. The following section shows the list of manually installed plugins:

(...)
2025-07-17 08:13:31 +0000: [Diagtool] [INFO] [Collect] fluent-package manually installed gem information is stored in /tmp/20250717081331/output/gem_local_list.output
2025-07-17 08:13:31 +0000: [Diagtool] [INFO] [Collect] fluent-package manually installed gems:
2025-07-17 08:13:31 +0000: [Diagtool] [INFO] [Collect]   * fluent-plugin-remote_syslog
(...)

In this example, the only manually installed plugin is fluent-plugin-remote_syslog. The list is also saved to a file:

  • /{output_directory}/{execution_timestamp}/output/gem_local_list.output

For the above case, the list was saved to /tmp/20250717081331/output/gem_local_list.output.

If you are using a version earlier than v5.0.2, the bundled fluent-diagtool is outdated. Please update it in advance:

$ sudo fluent-gem install fluent-diagtool

If you cannot update fluent-diagtool, obtain the list of plugins with:

$ fluent-gem list fluent-plugin

Note: On fluent-package v5.0.2 for Windows or earlier, fluent-diagtool is not available due to a known issue. Use fluent-gem list fluent-plugin instead.

2. Stop the Fluentd service

Stop any running Fluentd service(s). If multiple Fluentd services are running, stop them in the order: forwarders first, then aggregators.

3. Back up registry settings (Windows only)

On Windows, back up registry settings needed for rollback. Run the following command in PowerShell or Command Prompt as an administrator:

> reg export HKLM\System\CurrentControlSet\Services\fluentdwinsvc C:\fluent-package-5_fluentdwinsvc.reg

4. Install Fluent Package v6 LTS

Install Fluent Package v6 LTS.

Example for RPM Package (Red Hat Linux):

$ curl -fsSL https://fluentd.cdn.cncf.io/sh/install-redhat-fluent-package6-lts.sh | sh

Please refer to the official documentation for each environment:

5. Reinstall plugins

The manually installed plugins need to be reinstalled. Reinstall the plugins identified in step 1.

Example:

$ sudo fluent-gem install fluent-plugin-remote_syslog

6. Restart the Fluentd service

Restart the Fluentd service(s) you stopped in step 2. If multiple services exist, start them in the order from aggregators to forwarders.

Note: Zero-Downtime Update Settings (non-Windows)

From the next update onward, you can perform upgrades without stopping the service using the zero-downtime update feature (not supported on Windows).

You can configure how Fluentd restarts after an update:

  • auto (default): automatically performs zero-downtime restart after update
  • manual: requires manual zero-downtime restart, disabling automatic plugin reinstallation and restart

This setting can be changed anytime and does not require restarting Fluentd itself.

For details, see:

Rollback from Fluent Package v6 LTS to v5

1. Stop the Fluentd service

Stop running Fluentd services, in the order from forwarders to aggregators.

2. Install Fluent Package v5 LTS

On Linux, simply reinstall Fluent Package v5 LTS on top of v6. No need to uninstall v6 beforehand. On Windows, uninstall Fluent Package v6 LTS first, then install v5 LTS.

Manually installed plugins remain on the system, so after rollback they are still available. No reinstallation is required.

3. Restore the registry (Windows only)

On Windows, restore the registry with the following command (admin PowerShell or Command Prompt):

> reg import C:\fluent-package-5_fluentdwinsvc.reg

This restores Windows service auto-start settings and startup command-line arguments.

4. Restart the Fluentd service

Restart the stopped Fluentd services in opposite order: aggregators first, then forwarders.

Download

Please see the download page.

Announcement

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 reached EOL in Dec, 2023.

And fluent-package v5 will reach EOL in end of 2025.

We strongly recommend upgrading to fluent-package v6 LTS.

Follow us on X

We have been posting information about Fluentd in Japanese on @fluentd_jp. We would appreciate it if you followed our X account.

There are some commercial supports for Fluentd, see Enterprise Services. If you use Fluentd on production, Let's share your use-case/testimonial on Testimonials page. Please consider to feedback Use-Case/Testimonials via GitHub.

Subscribed to the RSS feed here.

Written by ClearCode, Inc.

ClearCode, Inc. is a software company specializing in the development of Free Software. We maintain Fluentd and its plugin ecosystem, and provide commercial support for them.