Redis Add-ons


Our Redis 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, sentinel logs, and haproxy logs 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> | <sentinel, or Redis log>


Raw Message:
<hostname> : [<customer [email protected]>] binary[pid]: <type info> | <sentinel or Redis 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> | <sentinel, or Redis log>


The telegraf plugin gathers stats from the redis INFO command. It then presents the information as "redis" statistics for server level stats and "redis_keyspace" statistics for database level stats. Documentation and example output is in the telegraf Redis plugin README.

Installing the telegraf add-on to your Compose deployment allows the statistics to be forwarded to either metrics service: Datadog or Librato.

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

Still Need Help?

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