Native convox logging information can be found here

Routing Logs to a 3rd Party

Convox supports routing your logs to any third party that can accept data from a syslog forwarder. You have two options, using the Resource Syslog or configuring the LogDriver to Syslog.

Resource Syslog

Using the resource Syslog, it will create a Lambda function that will gather logs from CloudWatch and forward them to your Syslog. It will enable convox logs and convox rack logs.

You can create a syslog forwarder with the following command:

$ convox rack resources create syslog [destination]

For example:

$ convox rack resources create syslog Url=tcp+tls://
Creating syslog-3785 (syslog)... CREATING

Additionally, you can pass a Format parameter to amend the default logging format to match the requirements of your receiving service.

For example for Datadog:

$ convox rack resources update syslog-3785 Format="123457890abcdef1234567890 <22>1 {DATE} {GROUP} {SERVICE} {CONTAINER} - - [metas ddsource=\"{GROUP}\" ddtags=\"container_id:{CONTAINER}\"] {MESSAGE}" Url=tcp+tls://

The {DATE} / {GROUP} / {SERVICE} / {CONTAINER} / {MESSAGE} variables within the format are dynamically replaced with the correct values and injected into the log output in the required format.

You can view the forwarder setup at any time using convox rack resources info

$ convox rack resources info syslog-3785
Name     syslog-3785
Status   running
Options  Format=<22>1 {DATE} {GROUP} {SERVICE} {CONTAINER} - - {MESSAGE}
URL      tcp+tls://

In order to start sending logs from an app to the forwarder you need to link it to the app with convox rack resources link

$ convox rack resources link syslog-3785 --app example
Linked syslog-3786 to example

Some common 3rd party logging services include:

  • Papertrail

    • Go to Log Destinations to get the forwarding destination
    • The Default Format is suggested. (<22>1 {DATE} {GROUP} {SERVICE} {CONTAINER} - - {MESSAGE})
  • Datadog

    • Go to Syslog-Ng Integration to check the forwarding destination. This currently differs between the US site ( and the EU site (
    • Suggested Format="INSERT-YOUR-API-KEY-HERE <22>1 {DATE} {GROUP} {SERVICE} {CONTAINER} - [metas ddsource=\"{GROUP}\" ddtags=\"container_id:{CONTAINER}\"] {MESSAGE}" where you replace INSERT-YOUR-API-KEY-HERE with your Datadog API key 😉
  • LogDNA

    • Go to, select Syslog as your provider and then use the provided url as the syslog resource Url (with tcp+tls://)
    • Suggested Format="<22>1 {DATE} {GROUP} {SERVICE} {CONTAINER} {MESSAGE}"
  • Loggly

    • Syslog configuration is documented here
    • Suggested Format="<22>1 {DATE} {GROUP} {SERVICE} {CONTAINER} - [INSERT-YOUR-CUSTOMER-TOKEN-HERE@41058 tag=\"INSERT-YOUR-TAG-HERE\" ] {MESSAGE}" and replacing INSERT-YOUR-CUSTOMER-TOKEN-HERE with your Loggly customer token and INSERT-YOUR-TAG-HERE with a tag that describes your source

Syslog as the LogDriver

Using Syslog as the LogDriver will disable CloudWatch, all rack and apps logs will be redirect directly to your Syslog destination, be aware that convox logs and convox rack logs will not work if CloudWatch is not enabled. You must provide SyslogDestination when enabling Syslog as LogDriver. You can create a rack using with:

$ convox rack install aws -n ${rack-name} LogDriver=Syslog SyslogDestination="tcp+tls://"

Or you can set on an existing rack by setting the parameters:

$ convox rack params set LogDriver=Syslog SyslogDestination="tcp+tls://"

You can change the Syslog format using SyslogFormat:

$ convox rack params set SyslogFormat=rfc5424micro