-
Notifications
You must be signed in to change notification settings - Fork 4k
rabbitmqctl shovel_status: handle metrics #14278
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
Conversation
The ctl command got broken when metrics were added to the status. As we have the metrics now, we just report them.
|
how it was discovered? there is status command suite and it was green IIRC... yeah last commit in that PR was green - #13620 Point I'm making - looks like that SUITE was not enough, maybe worth adding test? |
|
Just using it. The command would never return anything. The test suite is not an end to end test, it skips all the formatting part and that is where the issue is. A test which used |
|
The failures are not flakes: |
|
This PR will be backported for |
For 4.1.4: rabbitmqctl shovel_status: handle metrics (backport #14278)
The rabbitmqctl command got broken a while back when metrics were added to the status e3430aa
The command stopped reporting any status.
This PR addresses that, and as we have the metrics available, we just include them in the status.
I don't think e3430aa made it into any release, otherwise this PR needs backporting.