Monitoring td-agent

This article covers how to monitor the td-agent daemon.

Table of Contents


Monitoring via HTTP

td-agent has a built-in monitoring agent to retrieve internal metrics in JSON via HTTP. Please 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.

Next, please restart the agent and get the metrics via HTTP.

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

Process Monitoring

Two ruby processes (parent and child) are executed. Please make sure 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 statuses with the following command. Two processes should be shown 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

Last modified: Aug 03 2015 00:01:48 UTC

If this article is incorrect or outdated, or omits critical information, please let us know. For all other issues, please see our support channels.