CloudAMQP ships broker logs to Coralogix via the OpenTelemetry Protocol (OTLP). Available on RabbitMQ and LavinMQ dedicated instances.
Link: https://www.coralogix.com
production
) and a
Subsystem Name
(identifies the specific service or node — defaults to the instance hostname).
Fields appear in Coralogix with OTel path prefixes:
resource.attributes.service.name
— your CloudAMQP cluster name
resource.attributes.host.name
— the individual node hostname
logRecord.attributes.appname
— always
rabbitmq
or
lavinmq
logRecord.severityNumber
— numeric severity (9 = INFO, 13 = WARN, 17 = ERROR)
logRecord.body
— the log message text
The
Application
column shows the Application Name you configured. The
Subsystem
column defaults to the node hostname (e.g.
my-cluster-01.rmq6.cloudamqp.com
) unless you override the Subsystem Name in the integration settings.
Note: The original Coralogix integration delivers logs via syslog and is planned for deprecation. This integration (Coralogix v2) is the recommended replacement.