There is a topic titled “Using the Dynatrace OneAgent SDK with forked child processes (only available on Linux)“on the URL
Does this mean on Windows shared agent can’t be used between Parent and Child processes?
Is there a way to trace communication between Parent and Child processes on Windows with oneagent SDK?
Answer by Alram L. ·
The fork API in that form exists on Unix like operating systems only. On Windows, the StartProcess API works in a completely other way and doesn't allow to share an agent between parent and child process therefore.
But that doesn't mean, that you can't trace between parent and child processes.
On Windows every process will start their own agent. You need to setup the OneAgent SDK for C/C++ in both processes (parent + child). To trace communication between them use (for example) Outgoing-/Incoming remotecall. You need to transport the tag (received from the OutgoingRemoteCallTracer) over communicationchannel being used by parent- and child process (e. g. named pipe, shared memory, ...).
Be aware, that initializing the SDK in every process is a expensive operation and may take some time. If your application starts child processes often (e. g. for every dispachted request; child processes then are short living), it would be better to redesign your application to use child processes that are alive for longer time.