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

Allow running with Micrometer metrics #688

Merged
merged 1 commit into from
Mar 18, 2021

Conversation

jmartisk
Copy link
Member

@jmartisk jmartisk commented Mar 18, 2021

replacement for #673 but this should be less intrusive and shouldn't need any changes on runtime sides

The MetricsService now automatically detects whether there is the Micrometer or MP Metrics API available and uses one of them (Micrometer is preferred).

Fixes #384

@jmartisk jmartisk requested a review from phillip-kruger March 18, 2021 08:02
@phillip-kruger
Copy link
Member

Thanks @jmartisk !!

@phillip-kruger phillip-kruger added this to the 1.1.2 milestone Mar 18, 2021
@phillip-kruger
Copy link
Member

Are you backporting to 1.0.x ?

@phillip-kruger phillip-kruger merged commit a176e1d into smallrye:main Mar 18, 2021
@jmartisk
Copy link
Member Author

Are you backporting to 1.0.x ?

I don't think it's necessary. Quarkus will be upgrading to MicroProfile 4 soon (and therefore SmallRye GraphQL 1.1), and strictly speaking this would be a breaking change for users who use the Micrometer Quarkus extension - because before this PR, metrics go through the Micrometer-MPMetrics bridge; and after this PR, they would be handled by micrometer directly, so there would be minor differences in behavior.

@jmartisk jmartisk deleted the main-issue-384 branch March 18, 2021 11:06
@phillip-kruger
Copy link
Member

Cool! Thanks !

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

Successfully merging this pull request may close these issues.

Abstract away MP Metrics dependency
2 participants