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

By @gomoripeti: Streams: two additional Prometheus metrics for connections #12765

Merged
merged 4 commits into from
Nov 20, 2024

Conversation

michaelklishin
Copy link
Member

This is #10275 by @gomoripeti re-submitted so that Actions have access to all the GH secrets.

gomoripeti and others added 4 commits November 19, 2024 19:13
So that they can be used from multiple test suites.

(cherry picked from commit cf8a00c)
Supports both per stream (detailed) and aggregated (metrics) values.

(cherry picked from commit e82058e)
The application is not always recompiled which causes tests to fail
because they cannot call `serial_number:usort/1`.

(cherry picked from commit 05a3733)
@michaelklishin
Copy link
Member Author

michaelklishin commented Nov 20, 2024

I have received no objections to this PR from other core team members.

@michaelklishin
Copy link
Member Author

This seems safe to backport to v4.0.x, too. It's a new metric in a node-local plugin.

@michaelklishin michaelklishin added this to the 4.0.4 milestone Nov 20, 2024
@michaelklishin michaelklishin merged commit 85dab98 into main Nov 20, 2024
271 checks passed
@michaelklishin michaelklishin deleted the rabbitmq-server-10275 branch November 20, 2024 15:21
@michaelklishin michaelklishin modified the milestones: 4.0.4, 4.1.0 Nov 20, 2024
@michaelklishin
Copy link
Member Author

@gomoripeti backporting to v4.0.x turned out to be more involved. If you would like to contribute a v4.0.x version of this PR, it will be considered, otherwise it will ship next year in 4.1.0.

michaelklishin added a commit that referenced this pull request Nov 20, 2024
@gomoripeti
Copy link
Contributor

thank you. This feature is not super urgent for us so 4.1.0 sounds good. And I take a note of manually backporting to 4.0.x if time permits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants