Use fluent-package commands and paths in language binding guides (#709)

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.

Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Author: Watson1978

language-bindings/java.md

@@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it
 </match>
 ```
 
-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)

language-bindings/nodejs.md

@@ -32,14 +32,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it
 </match>
 ```
 
-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)

language-bindings/perl.md

@@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it
 </match>
 ```
 
-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)

language-bindings/php.md

@@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it
 </match>
 ```
 
-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)

language-bindings/python.md

@@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it
 </match>
 ```
 
-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)

language-bindings/ruby.md

@@ -30,14 +30,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it
 </match>
 ```
 
-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)

language-bindings/scala.md

@@ -31,14 +31,11 @@ Configure Fluentd to use the [`forward`](../input/forward.md) input plugin as it
 </match>
 ```
 
-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)