The universal profiler will be capable of reporting collected stacktraces and corresponding trace-contexts back to the OTel SDK / agent where the samples were collected. Closes #43.
This done via a unix domain datagram socket as defined in the spec. The approach has already been proven to work in a PoC.
To not have to deal with blocking on native methods on Java Threads, we only support non-blocking access. The socket will be polled regularly for messages, most likely something around every 50ms.
@elastic/apm-agent-php : Would be great if you can have a look at the C++ part of this PR
The universal profiler will be capable of reporting collected stacktraces and corresponding trace-contexts back to the OTel SDK / agent where the samples were collected. Closes #43.
This done via a unix domain datagram socket as defined in the spec. The approach has already been proven to work in a PoC.
To not have to deal with blocking on native methods on Java Threads, we only support non-blocking access. The socket will be polled regularly for messages, most likely something around every
50ms
.@elastic/apm-agent-php : Would be great if you can have a look at the C++ part of this PR