Skip to content

Conversation

@dcorbacho
Copy link
Contributor

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.

The ctl command got broken when metrics were added to the status.
As we have the metrics now, we just report them.
@ikavgo
Copy link
Contributor

ikavgo commented Jul 24, 2025

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?

@dcorbacho
Copy link
Contributor Author

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 rabbitmqctl shovel_status with any shovel would have detected it.

@michaelklishin
Copy link
Collaborator

michaelklishin commented Jul 24, 2025

The failures are not flakes:

shovel_status_command_SUITE > non_parallel_tests > output_starting
    #1. {error,
            {{badmatch,{stream,[]}},
             [{shovel_status_command_SUITE,output_starting,1,
                  [{file,"shovel_status_command_SUITE.erl"},{line,97}]},
              {test_server,ts_tc,3,[{file,"test_server.erl"},{line,1796}]},
              {test_server,run_test_case_eval1,6,
                  [{file,"test_server.erl"},{line,1305}]},
              {test_server,run_test_case_eval,9,
                  [{file,"test_server.erl"},{line,1237}]}]}}

shovel_status_command_SUITE > non_parallel_tests > output_running
    #1. {error,
            {{badmatch,{stream,[]}},
             [{shovel_status_command_SUITE,output_running,1,
                  [{file,"shovel_status_command_SUITE.erl"},{line,117}]},
              {test_server,ts_tc,3,[{file,"test_server.erl"},{line,1796}]},
              {test_server,run_test_case_eval1,6,
                  [{file,"test_server.erl"},{line,1305}]},
              {test_server,run_test_case_eval,9,
                  [{file,"test_server.erl"},{line,1237}]}]}}

@michaelklishin michaelklishin changed the title Rabbitmqctl shovel_status: handle metrics rabbitmqctl shovel_status: handle metrics Jul 28, 2025
@michaelklishin michaelklishin added this to the 4.2.0 milestone Jul 28, 2025
@michaelklishin michaelklishin merged commit d39e18f into main Jul 28, 2025
557 of 559 checks passed
@michaelklishin michaelklishin deleted the shovel-metrics branch July 28, 2025 12:43
@michaelklishin
Copy link
Collaborator

This PR will be backported for 4.1.4.

michaelklishin added a commit that referenced this pull request Aug 5, 2025
For 4.1.4: rabbitmqctl shovel_status: handle metrics (backport #14278)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants