What changed
The previous integration delivered logs over syslog/TLS to Coralogix's legacy ingestion endpoints. Timestamps, PIDs, and severity levels arrived embedded in the message body, requiring a parsing pipeline in Coralogix before you could act on them.
The new integration sends logs via OTLP/HTTP to Coralogix's current ingress endpoints, using
Bearer token authentication. Logs arrive as structured records: severity is a typed field,
message content is clean, and each record carries resource attributes that Coralogix can act
on without any pipeline configuration. One of those attributes is
appname,
always set to
rabbitmq
or
lavinmq,
useful for filtering by broker type in LiveTail and Alerts.
Application and subsystem
Coralogix organizes logs around two dimensions: application and subsystem. The integration
maps directly to these, sending
cx.application.name
and
cx.subsystem.name
as resource attributes on every record. Application name captures the environment:
"production", "staging", "dev". Subsystem scopes within it; the form pre-fills the node
hostname by default, which on multi-node clusters gives you per-node granularity in
Coralogix automatically.
Setting up the integration
You'll need four things from Coralogix before opening the CloudAMQP console:
-
Send-Your-Data API Key.
Found in Coralogix under
Settings → API Keys.
The key starts with
cxtp_ - Region. Select the one that matches your Coralogix account. Eight regions are supported: EU1 (Ireland), EU2 (Stockholm), US1 (Ohio), US2 (Oregon), US3 (Iowa), AP1 (Mumbai), AP2 (Singapore), and AP3 (Jakarta).
-
Application name.
Your environment label, e.g.
production - Subsystem name. Scoped within the application; defaults to the node hostname.
Enter those in the Integrations tab of your instance in the CloudAMQP console and save. Logs will start arriving in Coralogix within a minute.
Migrating from the previous integration
For RabbitMQ customers: if you have the syslog-based integration active, the two can run in parallel. Set up the new integration, confirm logs are arriving in the expected structure, then remove the old one. The syslog-based integration is planned for deprecation.
Full details on the log format and setup are in the CloudAMQP Coralogix log integration documentation.
If you have questions, reach out to support@cloudamqp.com
