14 Feb 2022 10:07 AM
23 Feb 2022 11:33 AM
Hi @stephane_kies, have you checked in the OneAgent logs and Windows Event logs? I'm not sure if there will be more info in there, but it is worth a look.
Unfortunately, the only other way I'm aware of is to reach out to DT ONE and ask if they can check it on your behalf.
For Java processes, you should typically see something like -javagent: or -agentpath: which should hint you on the type of agent if you check "command line args".
23 Feb 2022 01:43 PM - edited 23 Feb 2022 01:44 PM
In Windows, in the Event Viewer, you should find it. The problem is that they are normally identified as UUIDs, but the following two are from Dynatrace:
The profiler was loaded successfully. Profiler CLSID: '{DA7CFC47-3E35-4C4E-B495-534F93B28683}'
The profiler was loaded successfully. Profiler CLSID: '{B7038F67-52FC-4DA2-AB02-969B3C1EDA03}'
These messages will typically occur when an app pool starts. If you get other CLSIDs, post them here and we will try to find out who they are.
23 Feb 2022 06:06 PM
I found the following profilers and their related CLSIDs - perhaps it will help you track down the conflicting ones?
Profiler nameProfiler identifier
App Dynamics | AppDynamics.AgentProfiler |
Dynatrace | DA7CFC47-3E35-4c-4e-B495-534F93B28683 B7038F67-52FC-4DA2-AB02-969B3C1EDA03 |
Diagnostic Policy Service | 555908D1-A6D7-4695-8E1E-26931D2012F4 |
IntelliTrace | 2AA1AA98-2CAA-4FCF-86CE-EFA007737E83 |
Microsoft App Insights | 324F817A-7420-4E6D-B3C1-143FBED6D855 COR_PROFILER_PATH D:\home\SiteExtensions\Microsoft.ApplicationInsights.AzureWebSites\Agent\MicrosoftInstrumentationEngine.dll |
SCOM APM | AD5651A8-B5C8-46ca-A11B-E82AEC2B8E78 |
JetBrains dotCover | 9AA5D52F-37E2-487D-AAEC-727478B8BDB5 |