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

[2.13] - Backport Vert.x Metrics support #30420

Merged
merged 3 commits into from
Jan 18, 2023

Conversation

cescoffier
Copy link
Member

@cescoffier cescoffier commented Jan 17, 2023

…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.
@quarkus-bot
Copy link

quarkus-bot bot commented Jan 17, 2023

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

  • title should preferably start with an uppercase character (if it makes sense!)

This message is automatically generated by a bot.

@quarkus-bot
Copy link

quarkus-bot bot commented Jan 17, 2023

/cc @ebullient (micrometer)

@cescoffier cescoffier requested a review from gsmet January 17, 2023 17:20
@cescoffier
Copy link
Member Author

@gsmet Not sure I understand the "PR contains merge commits", it should not.

@gsmet
Copy link
Member

gsmet commented Jan 18, 2023

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
@gsmet gsmet force-pushed the vertx-metrics-backport branch from e49c264 to 977e096 Compare January 18, 2023 08:28
@gsmet
Copy link
Member

gsmet commented Jan 18, 2023

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.

@gsmet gsmet added this to the 2.13.7.Final milestone Jan 18, 2023
@quarkus-bot
Copy link

quarkus-bot bot commented Jan 18, 2023

Failing Jobs - Building 977e096

Status Name Step Failures Logs Raw logs
JVM Tests - JDK 11 Build ⚠️ Check → Logs Raw logs
JVM Tests - JDK 11 Windows Build ⚠️ Check → Logs Raw logs
✔️ JVM Tests - JDK 17
✔️ JVM Tests - JDK 18

@gsmet gsmet merged commit 69f50d7 into quarkusio:2.13 Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants