You can monitor the Treasure Agent (td-agent) daemon to collect metrics or to troubleshoot your system.


  • Basic knowledge of Treasure Data.

  • Basic knowledge of td-agent.

Fluentd Metrics Monitoring

Monitoring via HTTP

td-agent has a built-in monitoring agent to retrieve internal metrics in JSON via HTTP. Add the following lines to your configuration file.

  type monitor_agent
  port 24220

disable_node_info (default true): Send system metrics, CPU / Memory / Disk, or not.

Restart the agent and get the metrics via HTTP.

$ curl http://host:24220/api/plugins.json

Monitoring with Prometheus or Datadog

Additionally, td-agent works with monitoring tools such as Prometheus, Datadog, etc. Our recommendation is to use Prometheus because Treasure Data collaborates with the CNCF (Cloud Native Computing Foundation).

Process Monitoring

Two ruby processes (parent and child) are executed. Ensure that these processes are running.

/usr/lib/fluent/ruby/bin/ruby /usr/sbin/td-agent
  --daemon /var/run/td-agent/
  --log /var/log/td-agent/td-agent.log

For td-agent on Linux, you can check the process status with the following command. You see the status of two processes if there are no issues.

$ ps w -C ruby -C td-agent --no-heading
32342 ?        Sl     0:00 /usr/lib/fluent/ruby/bin/ruby /usr/sbin/td-agent --daemon /var/run/td-agent/ --log /var/log/td-agent/td-agent.log
32345 ?        Sl     0:01 /usr/lib/fluent/ruby/bin/ruby /usr/sbin/td-agent --daemon /var/run/td-agent/ --log /var/log/td-agent/td-agent.log

Port Monitoring

td-agent opens the following ports by default. We recommend checking the availability of these ports.

  • TCP 8888 (HTTP)

  • TCP 24224 (Forward)

If you don’t send any data, the daemon doesn’t do anything.

Debug Port

A debug port for local communication is also opened.

  • TCP 24230

  • No labels