You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently upgraded our RabbitMQ clusters from 3.13.7 to 4.0.5 and have configured the default queue type to "quorum" for my default vhost.
I'm using the RabbitMQ integration of the Datadog Agent to monitor the nodes (one agent is installed on each node). Since the RabbitMQ upgrade, I now have a warning in my RabbitMQ management UI: "⚠ Deprecated features are being used. [Learn more]".
Looking at the deprecated features table:
We can see that the transient_nonexcl_queues feature is being used.
When I delete the aliveness-test queue created by the Datadog Agent, the deprecation warning disappears. Of course, it reappears as the agent re-creates the queue.
Also, I noticed that the aliveness-test queue created has an explicit classic queue type.
Does anybody else experience the same issue? Thanks!
The text was updated successfully, but these errors were encountered:
Hi Everyone,
I recently upgraded our RabbitMQ clusters from 3.13.7 to 4.0.5 and have configured the default queue type to "quorum" for my default vhost.
I'm using the RabbitMQ integration of the Datadog Agent to monitor the nodes (one agent is installed on each node). Since the RabbitMQ upgrade, I now have a warning in my RabbitMQ management UI: "⚠ Deprecated features are being used. [Learn more]".
Looking at the deprecated features table:
We can see that the
transient_nonexcl_queues
feature is being used.When I delete the
aliveness-test
queue created by the Datadog Agent, the deprecation warning disappears. Of course, it reappears as the agent re-creates the queue.Also, I noticed that the
aliveness-test
queue created has an explicitclassic
queue type.Does anybody else experience the same issue? Thanks!
The text was updated successfully, but these errors were encountered: