This Gauge has been already registered "http.server.active.requests"

[thibaultmeyer]

Describe the bug

When you start a server listening on http and https, you get a warning that the http.server.active.requests metric is already in use.

HTTP only

2025-02-27 16:11:09,977 INFO  [io.quarkus] (Quarkus Main Thread) MY_APP 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.19.1) started in 5.833s. Listening on: http://localhost:8080
2025-02-27 16:11:09,979 INFO  [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2025-02-27 16:11:09,979 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, micrometer, rest, rest-jackson, smallrye-context-propagation, smallrye-health, vertx]

HTTP + HTTPS

2025-02-27 16:13:12,331 WARN  [io.mic.cor.ins.MeterRegistry] (vert.x-acceptor-thread-0) This Gauge has been already registered (MeterId{name='http.server.active.requests', tags=[]}), the Gauge registration will be ignored. Note that subsequent logs will be logged at debug level.
2025-02-27 16:13:12,336 INFO  [io.quarkus] (Quarkus Main Thread) MY_APP 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.19.1) started in 6.761s. Listening on: http://localhost:8080 and https://localhost:8081
2025-02-27 16:13:12,337 INFO  [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2025-02-27 16:13:12,337 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, micrometer, rest, rest-jackson, smallrye-context-propagation, smallrye-health, vertx]

Expected behavior

No warnings. Maybe a tag to differentiate between HTTP and HTTPS?

Output of java -version

mandrel-java21-windows-amd64-23.1.5.0-Final

Quarkus version or git rev

3.19.1

Build tool (ie. output of mvnw --version or gradlew --version)

Maven 3.9.9

[geoand]

I can't reproduce this, so we'll have to have a reproducer for this.

Thanks

Never mind, I was able to reproduce this after all

[geoand]

@cescoffier @brunobat it seems like the entire io.quarkus.micrometer.runtime.binder.vertx.VertxHttpServerMetrics is run for both HTTP and HTTPS servers (and without providing any information on which server is being created).

How do you want to handle this?

[brunobat]

It the metric is already created we should reuse it.
I'm afraid we need to add a Tag and a new dimension to accomodate for http and https.
We should probably use the OTel semantic convention for this attribute: url.scheme

[geoand]

I'm afraid we need to add a Tag and a new dimension to accomodate for http and https.

Makes sense