Question about Quarkus and OpenTelemetry - Client resource naming?

[praiaJaeyoungChung]

Hi,

I maybe missing a very basic thing here but since picking up a recent Quarkus version bump (can't recall the exact version - I think we went from 3.12 to 3.17?) the open telemetry tag for trace.io.quarkus.opentelemetry.client.hits.by_http_status (or any client metrics for that matter) is giving hash like value for the resource identifier. This is making monitoring quite a challenge as these are not immediately clear what APIs / clients this is dealing with.

How can I assign a custom name to the client resource of my dependencies?

[cescoffier]

\CC @brunobat

[brunobat]

@praiaJaeyoungChung, what's trace.io.quarkus.opentelemetry.client.hits.by_http_status? Quarkus doesn't produce that.
In the resource part of the span we produce service_name and host_name, among others, but no resource_name or resource.
That might being added by a system property set in the service: quarkus.otel.resource.attributes
For more information, please check: https://quarkus.io/guides/opentelemetry#resource