If you're setting camel.metrics.enabled = true. Try removing it. Your metrics should still get published without it.
On Sat, 4 May 2024 at 18:29, Mikael Andersson Wigander <mikael.andersson.wigan...@pm.me.invalid> wrote: > Yes but that’s the thing. > > I have them both. > > /M > > Den 4 maj 2024 kl 19:02, James Netherton <[jamesnether...@gmail.com > ](mailto:Den 4 maj 2024 kl 19:02, James Netherton <<a href=)> skrev: > > > Hi, > > > > There is no extension for camel-micrometer-prometheus. You can use > > camel-quarkus-micrometer and add an additional dependency for > > quarkus-micrometer-registry-prometheus. > > > > <dependency> > > <groupId>io.quarkus</groupId> > > <artifactId>quarkus-micrometer-registry-prometheus</artifactId> > > </dependency> > > > > Then all of your metrics will be available on the /q/metrics endpoint. > > There's more information here: > > > > > https://camel.apache.org/camel-quarkus/next/reference/extensions/micrometer.html#extensions-micrometer-usage > > > > https://quarkus.io/guides/telemetry-micrometer > > > > -- > > James > > > > On Sat, 4 May 2024 at 17:17, Mikael Andersson Wigander > > <mikael.andersson.wigan...@pm.me.invalid> wrote: > > > >> Hi > >> > >> After upgrading my application to Quarkus 3.10.0 with camel 4.4.5 it > won’t > >> start because it complains about an extension not present in class path: > >> > >> camel-micrometer-prometheus. > >> > >> We use Metrics with Micrometer and Prometheus and don’t know what to do > >> now. > >> > >> Can’t find any migration guide covers this, only name changes to tags. > >> > >> Please advise! > >> > >> /M
