There are a handful of issues that could be stopping the app from reporting but since it is a .NET Core app in IIS, the first thing to check would be if the app is running In-Process or Out-Of-Process.   I suspect that the web application is running out-of-process and hosted by dotnet.exe process.  If that is the case, you will need to configure the web application as a standalone application. The following sample configuration demonstrates how to instrument a .NET Core standalone application hosted by the dotnet.exe : <?xml version="1.0" encoding="utf-8"?> <appdynamics-agent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <controller host="mycontroller.mycompany.com" port="8090" ssl="false"> <application name="My Business Application" /> </controller> <machine-agent /> <app-agents> <IIS> <applications /> </IIS> <standalone-applications> <standalone-application executable="dotnet.exe" command-line="MyApp.dll"> //command-line option instructs the agent to monitor only "MyApp" <tier name="DotNet Core Tier" /> </standalone-application> </standalone-applications> </app-agents> </appdynamics-agent> Here is a link to our documentation about setting up standalone applications: https://docs.appdynamics.com/display/PRO45/Configure+the+.NET+Agent+for+Windows+Services+and+Standalone+Applications Also, here is a link to the Microsoft docs about the Hosting models for ASP.NET Core if you need help determining what hosting model is set for your application. https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1#out-of-process-hosting-model ... View more

It appears there may be another APM tool installed on the machine.  Since there can only be one .NET profiler configured at a time, you will want to be sure to uninstall whichever tool is there and then rerun the AppDynamics .NET agent installer.  If you are unsure of which APM tool is currently installed, you can run the following command in the Windows Run tool to launch the Environment Variables editor and check the value that is stored in the COR_PROFILER variable.   rundll32 sysdm.cpl,EditEnvironmentVariables With that value, you should be able to run a quick web search to see which tool that profiler ID is associated with. ... View more