.NET Microservices Agent
To monitor standalone applications on different platforms, install the .NET microservices agent on the solution of your choice. Where and how you install the .NET microservices agent depends on your platform—for example, Azure App Service or Service Fabric—and what applications you want to monitor. For example, you can now monitor applications developed using .NET Core for Windows using the .NET microservices agent.
Note: You need the default
AppDynamicsConfig.json file in one of the following .NET Agent probing paths: <appfolder>\<appdll>.AppDynamicsConfig.json, <appfolder>\AppDynamicsConfig.json, or <profilerpath>\AppDynamicsConfig.json to ensure that the agent works. The application dll name should be without a .dll or .exe extension. Having the AppDynamicsConfig.json file placed in an application folder signals to the profiler that it needs to monitor the application. This limitation is put into place to avoid multiple applications from being instrumented on a Windows machine. Currently, we do not have this limitation on Linux.