@adityad I’ve seen something like this before. Our Netty instrumentation is a different package from our Play instrumentation, but both can be hit in the same request. As I understand it, if we see an http request come through PlayNettyServer’s http dispatcher (NettyDispatcher), we start a web transaction at that point and name it NettyDispatcher. Later in that request, if we encounter another framework class that we recognize, say a Play Controller, we’ll rename the request based on that class and method.
However, since Play 2.6.2 is not yet supported, the second step may not be happening. So the requests remain grouped under the generic name.
If I’m right, we can confirm it with a set of logs. I’m going to open a support ticket on your behalf, so that we can troubleshoot this more in depth. I’ll send you a link to the support ticket momentarily.
The solution may be to use XML Instrumentation to identify the Play Controller methods or similar and break out each code path under its own name. I can also enter a feature request for out-of-the-box support for Play 2.6.2.