From e00f0f6873221d6891c7e75d9885e4a136bcabc1 Mon Sep 17 00:00:00 2001 From: Shizuo Fujita Date: Thu, 8 Oct 2026 11:19:11 +0900 Subject: [PATCH] Use fluent-package commands and paths in language binding guides The seven language binding guides still told readers to restart td-agent with init.d or systemd and to check /var/log/td-agent/td-agent.log. td-agent has reached EOL, and fluent-package only ships a systemd unit named fluentd and logs to /var/log/fluent/fluentd.log. Also say Fluentd instead of td-agent or agent in the surrounding text. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Shizuo Fujita --- language-bindings/java.md | 15 ++++++--------- language-bindings/nodejs.md | 15 ++++++--------- language-bindings/perl.md | 15 ++++++--------- language-bindings/php.md | 15 ++++++--------- language-bindings/python.md | 15 ++++++--------- language-bindings/ruby.md | 15 ++++++--------- language-bindings/scala.md | 15 ++++++--------- 7 files changed, 42 insertions(+), 63 deletions(-) diff --git a/language-bindings/java.md b/language-bindings/java.md index 080c1b4f..8b2196f2 100644 --- a/language-bindings/java.md +++ b/language-bindings/java.md @@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it ``` -Restart agent after configuring. +Restart Fluentd after configuring. ```text -# for rpm/deb only -$ sudo /etc/init.d/td-agent restart - -# or systemd -$ sudo systemctl restart td-agent.service +# for fluent-package (rpm/deb) +$ sudo systemctl restart fluentd ``` ## Using `fluent-logger-java` @@ -85,7 +82,7 @@ Executing the above program will send the logs to Fluentd: $ java -jar test.jar ``` -The logs should be output to `/var/log/td-agent/td-agent.log` or the standard output of the Fluentd process via [`stdout`](../output/stdout.md) output plugin. +The logs should be output to `/var/log/fluent/fluentd.log` or the standard output of the Fluentd process via [`stdout`](../output/stdout.md) output plugin. ## Production Deployments @@ -106,12 +103,12 @@ Various [output plugins](../output/) are available for writing records to other ### High-Availability Configurations of Fluentd -For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for `td-agent`. This will improve the reliability of data transfer and query performance. +For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for Fluentd. This will improve the reliability of data transfer and query performance. * [High-Availability Configurations of Fluentd](../deployment/high-availability.md) ### Monitoring -Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for `td-agent`: +Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for Fluentd: * [Monitoring Fluentd](../monitoring-fluentd/overview.md) diff --git a/language-bindings/nodejs.md b/language-bindings/nodejs.md index 6d4d9b64..a7226559 100644 --- a/language-bindings/nodejs.md +++ b/language-bindings/nodejs.md @@ -32,14 +32,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it ``` -Restart agent after configuring. +Restart Fluentd after configuring. ```text -# for rpm/deb only -$ sudo /etc/init.d/td-agent restart - -# or systemd -$ sudo systemctl restart td-agent.service +# for fluent-package (rpm/deb) +$ sudo systemctl restart fluentd ``` ## Using `@fluent-org/logger` @@ -105,7 +102,7 @@ Run the app and go to `http://localhost:3000/` in your browser to send the logs $ node index.js ``` -The logs should be output to `/var/log/td-agent/td-agent.log` or the standard output of the Fluentd process via [`stdout`](../output/stdout.md) output plugin. +The logs should be output to `/var/log/fluent/fluentd.log` or the standard output of the Fluentd process via [`stdout`](../output/stdout.md) output plugin. ## Production Deployments @@ -126,12 +123,12 @@ Various [output plugins](../output/) are available for writing records to other ### High-Availability Configurations of Fluentd -For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for `td-agent`. This will improve the reliability of data transfer and query performance. +For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for Fluentd. This will improve the reliability of data transfer and query performance. * [High-Availability Configurations of Fluentd](../deployment/high-availability.md) ### Monitoring -Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for `td-agent`. +Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for Fluentd. * [Monitoring Fluentd](../monitoring-fluentd/overview.md) diff --git a/language-bindings/perl.md b/language-bindings/perl.md index d5cb7b9b..ba6cc68c 100644 --- a/language-bindings/perl.md +++ b/language-bindings/perl.md @@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it ``` -Restart agent after configuring. +Restart Fluentd after configuring. ```text -# for rpm/deb only -$ sudo /etc/init.d/td-agent restart - -# or systemd -$ sudo systemctl restart td-agent.service +# for fluent-package (rpm/deb) +$ sudo systemctl restart fluentd ``` ## Using `Fluent::Logger` @@ -68,7 +65,7 @@ Executing the script will send the logs to Fluentd: $ perl test.pl ``` -The logs should be output to `/var/log/td-agent/td-agent.log` or the standard output of the Fluentd process via [`stdout`](../output/stdout.md) output plugin. +The logs should be output to `/var/log/fluent/fluentd.log` or the standard output of the Fluentd process via [`stdout`](../output/stdout.md) output plugin. ## Production Deployments @@ -89,12 +86,12 @@ Various [output plugins](../output/) are available for writing records to other ### High-Availability Configurations of Fluentd -For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for `td-agent`. This will improve the reliability of data transfer and query performance. +For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for Fluentd. This will improve the reliability of data transfer and query performance. * [High-Availability Configurations of Fluentd](../deployment/high-availability.md) ### Monitoring -Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for `td-agent`. +Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for Fluentd. * [Monitoring Fluentd](../monitoring-fluentd/overview.md) diff --git a/language-bindings/php.md b/language-bindings/php.md index b71e298b..7687e7be 100644 --- a/language-bindings/php.md +++ b/language-bindings/php.md @@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it ``` -Restart agent after configuring. +Restart Fluentd after configuring. ```text -# for rpm/deb only -$ sudo /etc/init.d/td-agent restart - -# or systemd -$ sudo systemctl restart td-agent.service +# for fluent-package (rpm/deb) +$ sudo systemctl restart fluentd ``` ## Using `fluent-logger-php` @@ -68,7 +65,7 @@ Executing the script will send the logs to Fluentd: $ php test.php ``` -The logs should be output to `/var/log/td-agent/td-agent.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. +The logs should be output to `/var/log/fluent/fluentd.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. ## Production Deployments @@ -89,12 +86,12 @@ Various [output plugins](../output/) are available for writing records to other ### High-Availability Configurations of Fluentd -For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for `td-agent`. This will improve the reliability of data transfer and query performance. +For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for Fluentd. This will improve the reliability of data transfer and query performance. * [High-Availability Configurations of Fluentd](../deployment/high-availability.md) ### Monitoring -Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for `td-agent`. +Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for Fluentd. * [Monitoring Fluentd](../monitoring-fluentd/overview.md) diff --git a/language-bindings/python.md b/language-bindings/python.md index 8ba25415..f5e6dfa8 100644 --- a/language-bindings/python.md +++ b/language-bindings/python.md @@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it ``` -Restart agent after configuring. +Restart Fluentd after configuring. ```text -# for rpm/deb only -$ sudo /etc/init.d/td-agent restart - -# or systemd -$ sudo systemctl restart td-agent.service +# for fluent-package (rpm/deb) +$ sudo systemctl restart fluentd ``` ## Using `fluent-logger-python` @@ -67,7 +64,7 @@ Executing the script will send the logs to Fluentd: $ python test.py ``` -The logs should be output to `/var/log/td-agent/td-agent.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. +The logs should be output to `/var/log/fluent/fluentd.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. ## Production Deployments @@ -88,12 +85,12 @@ Various [output plugins](../output/) are available for writing records to other ### High-Availability Configurations of Fluentd -For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for `td-agent`. This will improve the reliability of data transfer and query performance. +For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for Fluentd. This will improve the reliability of data transfer and query performance. * [High-Availability Configurations of Fluentd](../deployment/high-availability.md) ### Monitoring -Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for `td-agent`. +Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for Fluentd. * [Monitoring Fluentd](../monitoring-fluentd/overview.md) diff --git a/language-bindings/ruby.md b/language-bindings/ruby.md index f38941a5..c0521ded 100644 --- a/language-bindings/ruby.md +++ b/language-bindings/ruby.md @@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it ``` -Restart agent after configuring. +Restart Fluentd after configuring. ```text -# for rpm/deb only -$ sudo /etc/init.d/td-agent restart - -# or systemd -$ sudo systemctl restart td-agent.service +# for fluent-package (rpm/deb) +$ sudo systemctl restart fluentd ``` ## Using `fluent-logger-ruby` @@ -62,7 +59,7 @@ Executing the script will send the logs to Fluentd: $ ruby test.rb ``` -The logs should be output to `/var/log/td-agent/td-agent.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. +The logs should be output to `/var/log/fluent/fluentd.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. ## Production Deployments @@ -83,12 +80,12 @@ Various [output plugins](../output/) are available for writing records to other ### High-Availability Configurations of Fluentd -For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for `td-agent`. This will improve the reliability of data transfer and query performance. +For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for Fluentd. This will improve the reliability of data transfer and query performance. * [High-Availability Configurations of Fluentd](../deployment/high-availability.md) ### Monitoring -Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for `td-agent`. +Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for Fluentd. * [Monitoring Fluentd](../monitoring-fluentd/overview.md) diff --git a/language-bindings/scala.md b/language-bindings/scala.md index ab0e0be4..74beed7b 100644 --- a/language-bindings/scala.md +++ b/language-bindings/scala.md @@ -31,14 +31,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it ``` -Restart agent after configuring. +Restart Fluentd after configuring. ```text -# for rpm/deb only -$ sudo /etc/init.d/td-agent restart - -# or systemd -$ sudo systemctl restart td-agent.service +# for fluent-package (rpm/deb) +$ sudo systemctl restart fluentd ``` ## Using `fluent-logger-scala` @@ -91,7 +88,7 @@ $ sbt > run ``` -The logs should be output to `/var/log/td-agent/td-agent.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. +The logs should be output to `/var/log/fluent/fluentd.log` or the standard output of the Fluentd process via the [`stdout`](../output/stdout.md) output plugin. ## Production Deployments @@ -112,12 +109,12 @@ Various [output plugins](../output/) are available for writing records to other ### High-Availability Configurations of Fluentd -For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for `td-agent`. This will improve the reliability of data transfer and query performance. +For high-traffic websites \(more than 5 application nodes\), we recommend using the high-availability configuration for Fluentd. This will improve the reliability of data transfer and query performance. * [High-Availability Configurations of Fluentd](../deployment/high-availability.md) ### Monitoring -Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for `td-agent`. +Monitoring Fluentd itself is also important. The article below describes the general monitoring methods for Fluentd. * [Monitoring Fluentd](../monitoring-fluentd/overview.md)