Micrometer metrics not resolving full path for inherited JAX-RS endpoints

[geisson-silva-ids]

Micrometer metrics not resolving full path for inherited JAX-RS endpoints

Hi everyone,

I'm experiencing an issue when generating Micrometer metrics in a Quarkus application. I'm using the extensions quarkus-micrometer-registry-prometheus and quarkus-resteasy-jackson.

My application uses superclasses to define common endpoint behaviors, and concrete classes extend these superclasses to implement or override specific endpoints.

To better illustrate the issue, I created a minimal example project:

Example

SuperclassResource.java

package br.inf.ids.laboratorio;

import jakarta.ws.rs.GET;

public class SuperclassResource {

    @GET
    public String getPath() {
        return "Superclass path";
    }
}

ConcreteResource.java

package br.inf.ids.laboratorio;

import jakarta.ws.rs.GET;
import jakarta.ws.rs.Path;

@Path("concrete")
public class ConcreteResource extends SuperclassResource {

    @GET
    @Path("outher-path")
    public String getImplemented() {
        return "Outher path in concrete class";
    }
}

In this example, SuperclassResource defines a GET endpoint, and ConcreteResource extends it and adds another endpoint.

Problem

When I check the Micrometer metrics at /q/metrics, the metrics for the inherited method do not include the full concrete class path.

Current metrics:

http_server_requests_seconds_count{method="GET",outcome="SUCCESS",status="200",uri="/concrete/outher-path"} 1.0
http_server_requests_seconds_count{method="GET",outcome="SUCCESS",status="200",uri="root"} 1.0

Expected metrics:

http_server_requests_seconds_count{method="GET",outcome="SUCCESS",status="200",uri="/concrete/outher-path"} 1.0
http_server_requests_seconds_count{method="GET",outcome="SUCCESS",status="200",uri="/concrete"} 1.0

Repository

You can find the full example here:
👉 https://github.com/geisson-silva-ids/quarkus-http-metrics-example

Steps to reproduce

1. Run the app with:

   mvn quarkus:dev

2. Call the endpoints:

   curl http://localhost:8080/concrete
   curl http://localhost:8080/concrete/outher-path

3. Access the metrics at:

   http://localhost:8080/q/metrics
   

4. Check the values for the http_server_requests_seconds_count metric

---

Does anyone know if this is a limitation of Quarkus or Micrometer, or if there's a workaround to ensure inherited endpoints reflect the full path in metrics?

Thanks in advance!

[quarkus-bot[bot]]

/cc @brunobat (micrometer), @ebullient (metrics,micrometer), @jmartisk (metrics)