Logs and Metrics Integrations

This feature is available on dedicated instances.

The CloudAMQP team monitors your servers and RabbitMQ 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. It allows you to get a good overview of how your system is doing and get logs and metrics into the same place as you have your other systems monitored.

Integrations are not covered by the SLA. Please email us at support@cloudamqp.com if you want more details about exporting metrics or logs.

Logging

CloudAMQP can ship logs to: Grafana Cloud (Loki), Datadog, CloudWatch, Papertrail, Logentries, Google Stackdriver, Loggly, Splunk, Splunk V2, Coralogix, Azure Monitor, DataSet (Scalyr),

Several of these destinations receive logs through the CloudAMQP OpenTelemetry Collector pipeline (currently Grafana Cloud and Splunk V2). Logs arrive as structured events with severity levels and resource attributes, so no parsing rules or log pipelines are required on the destination side.

Each event carries the following OpenTelemetry 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. For example, Grafana Cloud's Loki exposes them as service_name and host_name, and Splunk exposes the severity as severity_text (e.g. info, warning, error).

Grafana Cloud (Loki) Logs

Link: https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/

CloudAMQP ships broker logs to Grafana Cloud, stored in Loki, via the OpenTelemetry protocol (OTLP).

To set up, sign in to the Grafana Cloud Portal, select your stack from the organization overview, and click Configure on the OpenTelemetry tile. There you will find:

Your OTLP endpoint — it looks like https://otlp-gateway-prod-<region>.grafana.net/otlp
Your numeric instance ID — this is used as the username
An API token — generate one on that page with at minimum the logs:write scope, or use a Service Account token with the MetricsPublisher role

Enter the endpoint URL, instance ID, and API token in the integration form in the CloudAMQP console and click Save to activate the integration.

Once connected, find your logs in Grafana by opening Explore, selecting the Loki data source, and querying by cluster or node:

{service_name="your-cluster-name"}
{host_name="your-cluster-name-01"}

Datadog Logs

Link: https://docs.datadoghq.com/logs/

Get your Datadog API key at app.datadoghq.com and enter the API key, region, and optional tags.

Example message for CloudAMQP cluster quick-gray-porcupine with user optional tags env:example

{
  "ddsource": "cloudamqp",
  "ddtags": "env:example",
  "hostname": "quick-gray-porcupine-01",
  "message": "2025-03-25 11:07:02.552827+00:00 [info] <0.10.0> Time to start RabbitMQ: 13283 ms\n",
  "service": "quick-gray-porcupine"
}

Note, if service is set as an optional tag when creating the integration it will override the service attribute, this applies for all integrations created after July 1, 2025.

CloudWatch Logs

Link: https://aws.amazon.com/cloudwatch

Create an IAM user with programmatic access and the following permissions: CreateLogGroup, CreateLogStream, DescribeLogGroups, DescribeLogStreams, and PutLogEvents. Select the AWS region and enter the user's Access Key and Secret Key in the fields.

Papertrail Logs

Link: https://www.papertrail.com

Create a Papertrail endpoint via https://papertrailapp.com/systems/setup and enter the endpoint address in the Address field.

Logentries Logs

Link: https://www.logentries.com

Create a Logentries token at https://logentries.com/app#/add-log/manual and enter it in the Token field.

Google Stackdriver Logs

Link: https://cloud.google.com/stackdriver

Steps to generate a credentials file with permissions to write logs into Stackdriver:

Sign in to your Google Cloud account
Go to IAM & admin
Click Service accounts
Click + Create Service Account
Give it an appropriate name and click Create
Add role "Logs Writer," no other roles are needed
In Step 3, click Create key and select Key type: JSON
Download the file to your computer
Select the file in the form below and click Save
You will find your logs by selecting your CloudAMQP hostname in the 'Log name' dropdown under 'Logs Explorer'.

Loggly Logs

Link: https://www.loggly.com

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

Splunk Logs

Link: https://www.splunk.com

Create a HTTP Event Collector token at https://<your-splunk>.cloud.splunk.com/en-US/manager/search/http-eventcollector and enter the token and the endpoint address into the respective fields.

Splunk V2 Logs

Link: https://www.splunk.com

Splunk V2 ships broker and system logs to your Splunk HTTP Event Collector (HEC) endpoint via the OpenTelemetry Collector.

To set up:

In Splunk, go to Settings → Data inputs → HTTP Event Collector and create a new token. On the token, you must set a default index (the destination where CloudAMQP events will land), and indexer acknowledgement must be disabled. Events do not include an explicit index field, so without a default index on the token they will be rejected by Splunk.
Your HEC URL looks something like https://<your-instance-id>.splunkcloud.com:443/services/collector
In the CloudAMQP console, open Integrations → Splunk V2 and enter the HEC endpoint, the token, and (optionally) a source type. Leave source type blank to use the token's default.

Coralogix Logs

Link: https://www.coralogix.com

CloudAMQP ships broker logs to Coralogix via the OpenTelemetry protocol (OTLP/HTTP).

To set up, log in to your Coralogix account and go to Settings → API Keys → Send Your Data. Copy the Send-Your-Data API key and enter it in the Send-Your-Data API Key field in the CloudAMQP console.

Select the Region matching your Coralogix account — this determines which OTLP ingress endpoint is used.

Application Name and Subsystem Name identify the source of your logs in Coralogix. Application Name is typically the environment (e.g. production ) and Subsystem Name identifies the specific service or node (defaults to the instance hostname). These map to the cx.application.name and cx.subsystem.name attributes in Coralogix.

Each log record includes the following attributes:

service.name — your CloudAMQP cluster name
host.name — the individual node hostname, useful on multi-node clusters
appname — always rabbitmq or lavinmq
cx.application.name — the Application Name you configured
cx.subsystem.name — the Subsystem Name you configured
Severity — mapped from the journald PRIORITY field to the OpenTelemetry severity spec

Legacy syslog Coralogix integration: The original Coralogix integration delivers logs via syslog and is planned for deprecation.

Azure Monitor Logs

Link: https://learn.microsoft.com/en-us/azure/azure-monitor/overview

You will need to have a Log Analytics Workspace, a Data Collection Endpoint and a Data Collection Rule and a table in your workspace. Set it up by following this tutorial. Logs Ingestion Tutorial. You will need to enter the Directory (tenant) ID, Application (client) ID, Application secret, DCE URI, Table name and DCR ID in the respective fields.

DataSet (Scalyr)

Link: https://app.scalyr.com

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

Metrics

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.

CloudAMQP offers metrics integrations to:

Azure Monitor Metrics

CloudWatch Metrics

Link: https://aws.amazon.com/cloudwatch

For CloudWatch, we have three integrations. The first CloudWatch integration has been around for a long time, and during that time, CloudWatch has evolved. We didn't want to break usage for all customers using the existing one, so we added a new integration to leverage some new features in CloudWatch. The third version export Prometheus metrics.

Librato Metrics

Link: https://www.librato.com

Datadog Metrics

Link: https://www.datadoghq.com/

For Datadog, we have three integrations. The first Datadog integration has been around for a long time. Version two matches all metrics to the dashboards in Datadog, when you activate this integration, the dashboards RabbitMQ - Overview and RabbitMQ - Metrics will get populated with data automatically. Third version does the same, but it matches the dashboard RabbitMQ - Overview (OpenMetrics Version) since it exports Prometheus metrics.

Dynatrace Metrics

Link: https://www.dynatrace.com

NewRelic Metrics

Link https://newrelic.com

For New Relic we have two integrations. New Relic V3 exports server and broker metrics in Prometheus format.

Google Stackdriver Metrics

https://cloud.google.com/stackdriver

For Stackdriver we have two integrations. Stackdriver V2 exports server and broker metrics in Prometheus format.

Splunk Metrics

Link: https://www.splunk.com

For Splunk we have two integrations. Splunk V2 exports server and broker metrics in Prometheus format.

Introduction

CloudAMQP Console

RabbitMQ

LavinMQ

Monitoring

Networking

Connectors

Maintenance

Migration Guides

Tutorials

Marketplaces

Features

Protocols

Code Sample

MQTT Code Sample

Logs and Metrics Integrations

Logging

Grafana Cloud (Loki) Logs

Datadog Logs

CloudWatch Logs

Papertrail Logs

Logentries Logs

Google Stackdriver Logs

Loggly Logs

Splunk Logs

Splunk V2 Logs

Coralogix Logs

Azure Monitor Logs

DataSet (Scalyr)

Metrics

Azure Monitor Metrics

CloudWatch Metrics

Librato Metrics

Datadog Metrics

Dynatrace Metrics

NewRelic Metrics

Google Stackdriver Metrics

Splunk Metrics