Treasure Data provides td-agent to collect server-side logs and events and to import the data from Scala applications.


  • Basic knowledge of Scala.

  • Basic knowledge of Treasure Data, including the TD Toolbelt.

  • JVM, Scala, sbt v0.11 or later.

Installing td-agent

Install td-agenton your application servers. td-agent sits within your application servers, focusing on uploading application logs to the cloud.

The td-logger-java library enables Scala applications to post records to their local td-agent. td-agent, in turn, uploads the data to the cloud every 5 minutes. Because the daemon runs on a local node, the logging latency is negligible.

td-agent Install Options

To install td-agent, run one of the following commands based on your environment. The agent program is installed automatically by using the package management software for each platform like rpm/deb/dmg.

RHEL/CentOS 5,6,7

$ curl -L | sh

Ubuntu and Debian

# 18.04 Bionic
$ curl -L | sh
# 16.04 Xenial (64bit only)
$ curl -L | sh
Legacy support for EOL versions is still available
# 14.04 Trusty
$ curl -L | sh
# 12.04 Precise
$ curl -L | sh
# Debian Stretch (64-bit only) $ curl -L | sh
# Debian Jessie (64-bit only)
$ curl -L | sh
# Debian Squeeze (64-bit only)
$ curl -L | sh

Amazon Linux

You can choose Amazon Linux 1 or Amazon Linux 2. Refer to Installing td-agent on Amazon Linux.

MacOS X 10.11+

$ open ''

MacOS X 10.11.1 (El Capitan) introduced some security changes. After installing the td-agent, edit the /Library/LaunchDaemons/td-agent.plist file to change /usr/sbin/td-agent to /opt/td-agent/usr/sbin/td-agent.

Windows Server 2012+

The Windows installation requires multiple steps. Complete the steps documented:

Opscode Chef (repository)

You can read more about the repository.

$ echo 'cookbook "td-agent"' >> Berksfile
$ berks install

AWS Elastic Beanstalk is also supported. Windows is not supported.

Modifying /etc/td-agent/td-agent.conf

Next, specify your API key by setting the apikey option. You can retrieve your API key from your profile in TD Console. Set the apikey option in your td-agent.conf file.

# Treasure Data Input and Output
  type forward
  port 24224
<match td.*.*>
  type tdlog
  apikey YOUR_API_KEY
  buffer_type file
  buffer_path /var/log/td-agent/buffer/td
  use_ssl true

YOUR_API_KEY should be your actual apikey string. Using a [write-only API key](access-control#rest-apis-access) is recommended.

Restart your agent when the following lines are in place.

# Linux
$ sudo /etc/init.d/td-agent restart

# MacOS X
$ sudo launchctl unload /Library/LaunchDaemons/td-agent.plist
$ sudo launchctl load /Library/LaunchDaemons/td-agent.plist

td-agent now accepts data via port 24224, buffers the data (var/log/td-agent/buffer/td), and automatically uploads the data into the cloud.

Using td-logger-java

First, add the following lines to build.sbt. The logger’s revision information can be found in CHANGES.txt.

If you need an all-in-one jar file, we provide one at

/* in build.sbt */
// Dependencies
libraryDependencies ++= Seq(
  "com.treasuredata" % "td-logger" % "${logger.version}"

Next, configure your file using the following commands:


Finally, insert the following lines into your application to initialize and post records. You can read more information about the API.

import java.util.Properties
import com.treasure_data.logger.TreasureDataLogger
import scala.collection.JavaConverters._

object Main {
  def main(args: Array[String]) {
    var props = System.getProperties();
    var LOG = TreasureDataLogger.getLogger("test_db");

    var map = Map("from" -> "userA", "to" -> "userB");
    LOG.log("follow", map.asJava.asInstanceOf[java.util.Map[String, java.lang.Object]]);

This example expects the following structure.

  • project_dir/build.sbt

  • project_dir/src/main/scala/Main.scala

  • project_dir/src/main/resources/

Confirming Data Import

First, execute the preceding program.

$ sbt compile run

Sending a SIGUSR1 signal flushes td-agent’s buffer. Upload starts immediately.

# Linux
$ kill -USR1 `cat /var/run/td-agent/`

# MacOS X
$ sudo kill -USR1 `sudo launchctl list | grep td-agent | cut -f 1`

To confirm the data upload, use td tables.

$ td tables
| Database   | Table      | Type | Count     |
| test_db    | follow     | log  | 1         |

Production Deployments

High-Availability Configurations of td-agent

For high-traffic websites (more than 5 application nodes), use a high availability configuration of td-agent to improve data transfer reliability and query performance.

Monitoring td-agent

Monitoring td-agent itself is also important. Refer to the following document for general monitoring methods for td-agent:

td-agent is fully open-sourced under the Fluentd project.

Next Steps

We offer a schema mechanism that is more flexible than that of traditional RDBMSs. For queries, we leverage the Hive and Presto Query Languages.

  • No labels