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
Wireshark is superior in nearly every way and rabbitmq_tracing was never meant to be used in production.
The only case where this plugin is superior to Wireshark is direct Erlang client publishing, that is, Shovels or Federation links that connect to localhost. This is not relevant to 99.9% of applications that are not in Erlang and do not run on RabbitMQ nodes.
The text was updated successfully, but these errors were encountered:
In many cases it's easier to use tracing to see what actually reaches RabbitMQ and the queues, what is the outcome of routing the message. Also, many people use it as an audit log of messages (which we do not recommend, but still).
Not sure what's the reasoning for removing it, but I think it is useful for many users.
Wireshark is superior in nearly every way and
rabbitmq_tracing
was never meant to be used in production.The only case where this plugin is superior to Wireshark is direct Erlang client publishing, that is, Shovels or Federation links that connect to
localhost
. This is not relevant to 99.9% of applications that are not in Erlang and do not run on RabbitMQ nodes.The text was updated successfully, but these errors were encountered: