When monitoring REST-based web services, the namespace value is not the same URI-type as for SOAP-based web services
Why is the namespace captured in a different way for REST WebServices?
From an example WADL file for Jersey web services
<ns0:doc xmlns:ns1="http://jersey.java.net/" ns1:generatedBy="Jersey: 2.22.4 2016-11-30 13:33:53"/>
<ns0:doc xmlns:ns2="http://jersey.java.net/" ns2:hint="This is simplified WADL with user and core resources only. To get full WADL with extended resources use the query parameter detail. Link: http://apmhost:7001/jerseyartifact/webapi/application.wadl?detail=true"/>
<ns0:method id="getIt" name="GET">
The namespace is derived from the resource path
The operation name is derived from the method
Note the resources base is similar to the namespace reported from SOAP-based web services
Release : 10.7.0
Component : APM Agents
As per the design, the namespace is read from path annotation, and operation is identified on the method name.
It would require product enhancement to use the resources base as the namespace metric
Documented information on REST web services and supported frameworks