etcd Add-ons


etcdv2 is being deprecated

With the release of etcd3 from beta, Compose will soon no longer support etcd2 on the platform. The deprecation schedule is:
November 1st, 2017 - No more etcd2 provisions.
February 1st, 2018 - Official EOL
May 1st, 2018 - Start spinning down deployments.

Please plan on upgrading or deprovisioning your etcd2 deployments accordingly.


Our etcd deployments support the Syslog-NG add-on, with Papertrail or Loggly. It's billed at $9.00/mo


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

Logs are forwarded continuously from all the database capsules present on your deployment. 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> | <etcd log>


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

Still Need Help?

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