This article describes how to monitor Fluentd.
Fluentd can expose internal metrics via REST API, and works with monitoring tools such as
Datadog, etc. Our recommendation is to use
Prometheus, since we will be collaborating more in the future under the CNCF (Cloud Native Computing Foundation).
ruby processes (parent and child) are executed. Please make sure that these processes are running.
Here's an example for
/opt/td-agent/embedded/bin/ruby /usr/sbin/td-agent--daemon /var/run/td-agent/td-agent.pid--log /var/log/td-agent/td-agent.log
td-agent on Linux, check the process statuses like this:
$ ps w -C ruby -C td-agent --no-heading32342 ? Sl 0:00 /opt/td-agent/embedded/bin/ruby /usr/sbin/td-agent --daemon /var/run/td-agent/td-agent.pid --log /var/log/td-agent/td-agent.log32345 ? Sl 0:01 /opt/td-agent/embedded/bin/ruby /usr/sbin/td-agent --daemon /var/run/td-agent/td-agent.pid --log /var/log/td-agent/td-agent.log
There should be two processes if there is no issue.
Fluentd opens several ports according to the configuration file. We recommend checking the availability of these ports. The default port settings are shown below:
TCP 0.0.0.0 9880 (HTTP by default)
TCP 0.0.0.0 24224 (Forward by default)
A debug port for local communication is recommended for troubleshooting. The following configuration will be required for the debug port:
<source>@type debug_agentbind 127.0.0.1port 24230</source>
You can attach the process using the
fluent-debug command through
If this article is incorrect or outdated, or omits critical information, please let us know. Fluentd is an open-source project under Cloud Native Computing Foundation (CNCF). All components are available under the Apache 2 License.