Disable the micrometer metrics which are enabled by default #32721
-
Hi, I tried to disable the Build failure: Build failed due to errors
[error]: Build step io.quarkus.arc.deployment.ArcProcessor#validate threw an exception: javax.enterprise.inject.spi.DeploymentException: javax.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type io.micrometer.prometheus.PrometheusMeterRegistry and qualifiers [@Default]
- java member: io.strimzi.kafka.bridge.quarkus.MetricsReporter#meterRegistry
- declared on CLASS bean [types=[io.strimzi.kafka.bridge.quarkus.MetricsReporter, java.lang.Object], qualifiers=[@Default, @Any], target=io.strimzi.kafka.bridge.quarkus.MetricsReporter] which I think are reasonable since I think that disabling the property removes the classes required Is there some way I can disable the micrometer metrics or maybe a way to disable/ignore the endpoint |
Beta Was this translation helpful? Give feedback.
Answered by
ebullient
Apr 18, 2023
Replies: 1 comment 11 replies
-
/cc @brunobat (micrometer), @ebullient (metrics,micrometer), @jmartisk (metrics) |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You don't need to use the prometheus meter registry. You can (as I've shown) make your own.
Use the micrometer extension alone, and provide your own Micrometer MeterRegistry that does what you need and provides its own endpoint, or try what I've suggested on another discussion thread to replace the default prometheus meter registry so you can alter the scrape behavior that the default metrics handler invokes.