You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We are already running an .NET instrumentation from another company.
Unfortunately it is still needed.
We would like to use the Elastic .Net APM agent in conjunction with the profiler already used.
Describe the solution you'd like
We would like to run our Elastic Agent in conjunction with other .Net APM profilers
This would mean that the Elastic APM .Net agent is on-boarded to the ClrInstrumentationEngine
After that We could run more than one profiler simultaneously!
Thanks for sharing this @GeorgeGkinis. This looks really interesting. Unfortunately, we don't plan to reimplement the profiler, but I will see what the OTel team are doing and if this is on the radar for the OTel auto instrumentation. It appears that you could configure our profiler using the Raw Profiler Hook to achieve multi-profiler support.
Is your feature request related to a problem? Please describe.
We are already running an .NET instrumentation from another company.
Unfortunately it is still needed.
We would like to use the Elastic .Net APM agent in conjunction with the profiler already used.
We tried to use https://github.com/microsoft/CLRInstrumentationEngine but the MicrosoftInstrumentationEngine_x64.dll is not to be found in the Elastic APM directory structure.
Describe the solution you'd like
We would like to run our Elastic Agent in conjunction with other .Net APM profilers
This would mean that the Elastic APM .Net agent is on-boarded to the ClrInstrumentationEngine
After that We could run more than one profiler simultaneously!
Describe alternatives you've considered
We followed the steps described here:
https://github.com/microsoft/CLRInstrumentationEngine/blob/main/docs/getting_started.md
The text was updated successfully, but these errors were encountered: