GuidesAPI ReferenceSupportArticles

RabbitMQ Add-ons

Suggest Edits

Overview

Our RabbitMQ deployments support the following add-ons:

STOMP

The STOMP add-on provisions a HAProxy portal to recieve messages in STOMP format. Click on the Add button to start provisioning the new HAProxy portal. Once the process is finished, the STOMP entry on the Add-ons page will have a Configure button. Clicking on it will reveal the Connection string to send your messages to.

The portal will be listed in Deployment Topology on the Overview page with the role rabbitmq/_stomp.

MQTT

The MQTT add-on provisions a HAProxy portal to recieve messages in MQTT format. Click on the Add button to start provisioning the new HAProxy portal. Once the process is finished the MQTT entry on the Add-ons page will have a Configure button. Clicking on it will reveal the Connection string to send your messages to.

The portal will be listed in Deployment Topology on the Overview page with the role rabbitmq/_mqtt.

Syslog-NG

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, systemd 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.

Papertrail

Raw Message:
<timestamp> <hostname>: <binary[pid]>: <type info> | <systemd, HAProxy, or RabbitMQ log>

Loggly

Raw Message:
<hostname> : [<customer [email protected]>] <binary[pid]>: <type info> | <systemd, HAProxy, or RabbitMQ 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

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> | <systemd, HAProxy, or RabbitMQ log>

Telegraf

The telegraf add-on for RabbitMQ reads statistics from the RabbitMQ Management plug-in and are from the RabbitMQ Management HTTP Stats. The specific subset of stats is available in the telegraf RabbitMQ 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

Updated over 3 years ago