You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using matchPattern to replace the URI used with http metrics tags is error prone. The existing detection mechanism was cursory, and only worked for simple paths.
Implementation ideas
For ResteasyReactive, we have a chance to expose the known/used template path more directly as part of the SimplifiedResourceInfo associated with the RuntimeResource. We can still hide a lot of the gorpy details while providing a reasonable String representation of the matched URI.
For older Resteasy, this is harder, and a bit more expensive to find the bits required to put the URI together.
For undertow.... yuck? (still thinking about it)
The text was updated successfully, but these errors were encountered:
Description
Follow on from #14813
Using matchPattern to replace the URI used with http metrics tags is error prone. The existing detection mechanism was cursory, and only worked for simple paths.
Implementation ideas
For ResteasyReactive, we have a chance to expose the known/used template path more directly as part of the SimplifiedResourceInfo associated with the RuntimeResource. We can still hide a lot of the gorpy details while providing a reasonable String representation of the matched URI.
For older Resteasy, this is harder, and a bit more expensive to find the bits required to put the URI together.
For undertow.... yuck? (still thinking about it)
The text was updated successfully, but these errors were encountered: