Compose Database-as-a-Service Help and Documentation

Everything you need to know about Compose, Hosted or Enterprise, is here in our help system. Whether you run one database for your businesses' sole application or six different databases to support an entire corporation, we've got the information you need.

RethinkDB Add-ons


Our RethinkDB deployments support the following add-ons:


Configuration instructions for the syslog-ng add-on can be found on the Syslog-NG Setup page.

Logs are forwarded continuously from all the capsules present on your deployment; so you will see database logs from all the capsules in chronological order. For easier parsing, Compose adds a header to each log message that contains a timestamp, hostname, and process information.

As a result, the raw messages that arrive at your service will vary.


Raw Message: <timestamp> <hostname>: <binary[pid]>: <type info> | <RethinkDB log>


Raw Message: <hostname> : [<customer [email protected]>] <binary[pid]>: <type info> | <RethinkDB log>

NB: In addition to just displaying the raw information from syslog-ng, Loggly also applies some parsing by default. It does not recognize the format of our logs, so you may want to implement your own parsing or derived fields to make more effective use of the logs there.


Logentries is no longer available for new deployments or as a new add-on for existing deployments. The format is here for deployments where it is already configured.
Raw Message: <timestamp> <hostname>: <binary[pid]>: <type info> | <RethinkDB log>


Configuration instructions for the Telegraf add-on can be found on the Telegraf Setup page.

Telegraf is currently configured to send the following metrics:
rethinkdb.engine.queries.per.sec ```

###Still Need Help?

If this article didn't solve things, [summon a human]( and get some help

[//]: # (rethinkdb, 700)


Updated 2 years ago

RethinkDB Add-ons

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.