How to trace TCP custom service callers

[bonelli]

I have a Java program (instrumented with OneAgent) which functions as a TCP server for a custom protocol, and I successfully defined a custom service over it, I'm tracing single requests and extracting meaningful request attributes.

Now, I have a regular Java web service (an application server instrumented with OneAgent) that connects to this server and performs requests using client classes for this custom protocol, and I need Dynatrace to understand that the web service is performing these requests and link the requests from incoming to outgoing services.

I can't understand how to configure this behavior: how can I instrument the caller (the web service) in order to detect the invocation of my custom client class' methods and then link these invocation to the custom server requests?

[marco_irmer · Accepted solution]

I believe you would need to implement some custom instrumentation to ensure that trace details are added into the request from the client side, and then consumed on the server side. The OneAgent handles this out-of-the-box for common frameworks using protocols like HTTP, but since you have a custom protocol you'll have to do this with the OneAgent SDK on both sides as described here.