-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[2.13] - Backport Vert.x Metrics support #30420
Conversation
…s (including the one for the Vert.x SQL clients), Redis... The code is an adaptation of the Vert.x Micrometer pool metrics implementation to follow the Quarkus conventions.
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
|
/cc @ebullient (micrometer) |
@gsmet Not sure I understand the "PR contains merge commits", it should not. |
What's a bit more concerning is that CI didn't run at all. There's something weird going on. Let me have a look. |
- Added Vert.x client metrics (as close as possible to the pool metrics) - Added TCP (Net) client metrics - Added TCP (Net) server metrics - Added UDP metrics - Added event bus metrics - Added HTTP client metrics - Do not monitor the REST client as it's already tracked using a Rest client filter - Configure the metric names of various Vert.x clients to get the data collected correctly - this include reactive DB drivers, redis... - Tags and metrics names are aligned with the existing ones
e49c264
to
977e096
Compare
I think GitHub was in a weird state. I just amended the comment of the last commit and force pushed and everything is in order now and regular CI has started. |
Backport the Vert.x metrics support: