The .NET Agent comes packaged with a Machine Agent (AppDynamics Agent Coordinator service) which collects the hardware and infrastructure metrics from Windows Performance Monitor.
See the attached document which shows the mapping between metrics tha...
Hi Soundrajan,
Windows service will run a standalone executable internally, so you we recommended you to replace the windows service section with that of stand alone one. Windows service section was used with older agents. For latest agent we recom...
Hi Soundrajan,
Instead of using windows service configuration, please configure the exectable running behing as stand alone application, as mentioned in following document.
https://docs.appdynamics.com/display/PRO43/Configure+the+.NET+Agent+for+W...
Hi,
Following message will be logged by .Net runtime when it sees a process not to be instrumented by profiler.
NET Runtime version 4.0.30319.0 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler C...
HI Irhazi,
Apologies for late response as I was having technical issues with my laptop from couple of days.
Please upload the latest Event logs and DotNetAgent folder in the upload link provided to you. I dont see any data there as of now.
Rega...
Hi Irhazi,
From the event logs we see following .Net error:
.NET Runtime version 4.0.30319.34014 - Loading profiler failed. COR_PROFILER is set to an invalid CLSID: 'AppDynamics.AgentProfiler'. HRESULT: 0x800401f3. Process ID (decimal): 5756. ...