Logs and Metrics Integrations

This feature is available on dedicated instances.

The CloudAMQP team monitors your servers and brokers to make sure that the service is online and performing well. But we have also built several integrations to third-party systems where we can export logs and/or metrics to give you visibility alongside the rest of your infrastructure.

Integrations are not covered by the SLA. Email support@cloudamqp.com if you have questions.

Log Integrations

OTel Log Integrations

The following integrations ship logs via the CloudAMQP OpenTelemetry Collector. Logs arrive as structured events with severity levels and resource attributes — no parsing rules or log pipelines are required on the destination side. Available on RabbitMQ and LavinMQ dedicated instances.

Each event carries the following resource attributes for filtering and grouping:

• service.name — your CloudAMQP cluster name
• host.name — the individual node hostname, useful on multi-node clusters
• appname — always rabbitmq or lavinmq
• Severity — mapped from the journald PRIORITY field to the OpenTelemetry severity spec (e.g. INFO = 9, WARN = 13, ERROR = 17)

Some destinations rename these attributes to match their own conventions. Details are in each integration's setup below.

CloudWatch

Ships broker logs to AWS CloudWatch Logs via OTLP using IAM role assumption — no access keys required.

Coralogix

Ships broker logs via OTLP.

Datadog

Ships broker logs to Datadog via OTLP.

Grafana Cloud (Loki)

Ships broker logs to Grafana Cloud via OTLP.

Splunk

Ships broker logs via HTTP Event Collector (HEC) and the OTel Collector. Also available as a Prometheus metrics integration.

Uptrace

Ships broker logs to Uptrace via OTLP.

Legacy Log Integrations

The following integrations use the CloudAMQP log-forwarding service and are available on RabbitMQ dedicated instances only.

Azure Monitor

Ships broker logs to Azure Monitor Logs.

CloudWatch

Ships broker logs to AWS CloudWatch Logs.

DataSet (Scalyr)

Create a Log Write Access key at app.scalyr.com/keys and enter it in the Token field.

Datadog

Ships broker logs to Datadog.

Google Stackdriver

Ships broker logs to Google Cloud Logging.

Logentries

Create a token at logentries.com and enter it in the Token field.

Loggly

Create a token at https://<your-company>.loggly.com/tokens and enter it in the Token field.

Papertrail

Create an endpoint via papertrailapp.com/systems/setup and enter the address in the Address field.

Splunk

Ships broker logs via HTTP Event Collector.

Metrics Integrations

With metrics integrations, you can filter what metrics to send based on regular expressions for queues and vhosts. You can also decide if you want to include metrics for auto-delete queues. We send metrics every 60 seconds by default, but this value can be changed to 10 seconds or higher.

Prometheus Metrics

The following integrations export server and broker metrics in Prometheus format via the CloudAMQP OpenTelemetry Collector. Available on RabbitMQ 3.10+ and LavinMQ dedicated instances.

Azure Monitor

Exports metrics to Azure Monitor via the OTel Collector.

CloudWatch V3

Exports metrics to AWS CloudWatch via the OTel Collector.

Datadog V3

Exports metrics to Datadog via the OTel Collector.

Dynatrace

Exports metrics to Dynatrace via the OTel Collector.

NewRelic V3

Exports metrics to NewRelic via the OTel Collector.

Google Stackdriver V2

Exports metrics to Google Cloud Monitoring via the OTel Collector.

Splunk V2

Exports metrics to Splunk via the OTel Collector. Also available as an OTel log integration.

Legacy Metrics

The following integrations use the CloudAMQP legacy metrics agent.

CloudWatch and CloudWatch V2

Superseded by CloudWatch V3.

Datadog and Datadog V2

Superseded by Datadog V3.

Librato

Legacy metrics integration for Librato.

NewRelic

Superseded by NewRelic V3.

Google Stackdriver

Superseded by Stackdriver V2.

Splunk

Superseded by Splunk V2.