Built for each other
Uptrace was designed around OpenTelemetry from the start — OTLP is its native protocol, not an adaptation. LavinMQ enters the observability space on the same foundation. The result is that broker logs land in Uptrace as first-class records: severity as a proper field, clean message content, no parsing rules needed on the Uptrace side.
For teams already running Uptrace for their application observability, broker logs from LavinMQ now fit into the same platform without any extra tooling.
Getting started
The integration takes a single value: your Uptrace DSN. Find it in your Uptrace project under
Settings → Projects.
It looks like
https://token@otlp.uptrace.dev/project_id
The DSN encodes your endpoint and authentication in one string.
Paste it into the
Integrations
tab for your instance in the CloudAMQP console and save. Logs will start arriving in Uptrace
within a minute, queryable by
service.name
(your cluster) and
host.name
(the individual node on multi-node clusters).
Read more in our CloudAMQP Uptrace log integration documentation.
If you have questions, reach out to support@cloudamqp.com
