trace resource grouping overly normalized, not showing full path

[polson-jama]

Tracer Version(s)

1.32.0

Java Version(s)

17

JVM Vendor

Oracle JDK

Bug Report

We have found that the resource name grouping found in our service endpoint page is grouped/normalized to such a high degree that it borders on uselessness. for instance, the top resource usage for our main application service is /rest/, which encompases a very broad range of resources where we would really need this to be broken down more into all the various /rest/ endpoints we actually have. This is also true for other base level endpoints being reported instead of individual endpoints like /ui/ and /attachment/**. We do have other endpoints that are not normalized in this overzealous way, and so I do presume this is a bug rather than intentional behavior.

These resources that are showing this issue are coming from mostly one service, that is currently using java 17 and the java trace agent version 1.32.0.

Expected Behavior

I expect the resource page (and the resources shown in the trace details) to be the full api endpoint being used, not just the first level deep in the structure, followed by wildcards.

Reproduction Code

No response