@Maximiliano.Guillen  - Starting with .Net msi agent version 20.3.x, the .NET Agent MSI installer for Windows now includes support for .NET Core applications, enabling unified management of .Net Core and full framework applications on Windows. The agent monitors .NET Core applications for IIS out of the box, if automatic IIS mode is configured. So we would recommend to install the latest 21.x agent and validate the behavior. The MSI Installer bundles .NET Core agent with the existing .NET framework agent and creates appropriate environment variables.  Supported environments are identical to the previous .NET Agent.  .NET Core versions 2.0 and later are supported. IIS-hosted .NET Core applications are monitored similar to the .NET frameworks configured in automatic mode.  You can configure .NET Core applications in the  config.xml  file, just as you would configure .NET framework applications.  You have to manually configure .NET Core applications in the  config.xml  file in either of the following scenarios: You monitor ASP .NET core applications that are not hosted in-process, but are hosted in  dotnet.exe You currently monitor standalone applications So can you remove the Micro Services agent related configuration and try instrumenting with latest MSI agent available on download.appdynamics.com for the respective .net core sites. Make sure to configure the sites manually in config.xml and provide same tier and node names so that it should start reporting under the same node. Also make sure at system level CORECLR_PROFILER is needed to be set to "AppDynamics.AgentProfiler" for msi agent to instrument the .net core applications.  Please restart Appdynamics Coordinator Service and following that please restart IIS and apply fresh load on the applications and let us know the behavior ? Let us know if you still face any issues. ... View more

@Maximiliano.Guillen - You need to specify node name as its missing in you JSON using "node": "" tag or setting APPDYNAMICS_AGENT_NODE_NAME environment variable. ... View more

@Maximiliano.Guillen - Yes you can keep in any folder we just need to make sure all the AppD dlls are also present their. ... View more

@Virsec.Ops - Starting with .Net msi agent version 20.3.x, the .NET Agent MSI installer for Windows now includes support for .NET Core applications, enabling unified management of .Net Core and full framework applications on Windows. The agent monitors .NET Core applications for IIS out of the box, if automatic IIS mode is configured. So we would recommend to install the latest 21.x agent and validate the behavior. The MSI Installer bundles .NET Core agent with the existing .NET framework agent and creates appropriate environment variables.  Supported environments are identical to the previous .NET Agent.  .NET Core versions 2.0 and later are supported. IIS-hosted .NET Core applications are monitored similar to the .NET frameworks configured in automatic mode.  You can configure .NET Core applications in the  config.xml  file, just as you would configure .NET framework applications.  You have to manually configure .NET Core applications in the  config.xml  file in either of the following scenarios: You monitor ASP .NET core applications that are not hosted in-process, but are hosted in  dotnet.exe You currently monitor standalone applications So can you remove the Micro Services agent related configuration and try instrumenting with latest MSI agent available on download.appdynamics.com for the respective .net core sites. Make sure to configure the sites manually in config.xml and provide same tier and node names so that it should start reporting under the same node. Also make sure at system level CORECLR_PROFILER is needed to be set to "AppDynamics.AgentProfiler" for msi agent to instrument the .net core applications.  Please restart Appdynamics Coordinator Service and following that please restart IIS and apply fresh load on the applications and let us know the behavior ? Let us know if you still face any issues. ... View more