Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.x: consider removing rabbitmq_tracing from the distribution #11553

Closed
michaelklishin opened this issue Jun 24, 2024 · 2 comments
Closed

4.x: consider removing rabbitmq_tracing from the distribution #11553

michaelklishin opened this issue Jun 24, 2024 · 2 comments

Comments

@michaelklishin
Copy link
Member

michaelklishin commented Jun 24, 2024

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.

@razvanphp
Copy link

I read the blog post and this looks very promising.

One question tho, from our use-case: can we debug the mqtt and web-mqtt traffic in the same way?

Thank you!
R

@luos
Copy link
Contributor

luos commented Sep 6, 2024

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.

@michaelklishin michaelklishin closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants