Quarkus OpenTelemetry Rest Client Span Name with Route (URL Path Template)

[luneo7]

Description

I've read the OTEL spec and there it says that HTTP client span names SHOULD be {method}...
But it also says that:

Instrumentation MUST NOT default to using URI path as span name, but MAY provide hooks to allow custom logic to override the default span name.

A while back we already had Common URL Template path handling for client REST requests (https://github.com/quarkusio/quarkus/pull/17676/files#diff-7ec5f78d8d81fbcc3f6ddfbbaebd02aabf6bf0a843693411d955bdeba8a1d74eR56)... So can we maybe add a config parameter to change the behavior to the old way of creating rest client span names?

Having the name as {method} {urlPathTemplate} helps a lot while browsing the spans through the traces UI...

As right now everything (all rest clients in a app) are grouped as the HTTP methods (GET, POST, PUT....)

Implementation ideas

No response

[quarkus-bot]

/cc @brunobat (opentelemetry), @cescoffier (rest-client), @geoand (rest-client), @radcortez (opentelemetry)

[brunobat]

This was fixed on the server but not in the client...

[luneo7]

Oh, so it wasn't on purpose that it was removed? If that is the case I can tackle this if you would like 😁

[brunobat]

Please do @luneo7 🙏