This post assumes that you are sure the .NET Core agent is not creating logs for your application and that you have a Windows OS. If you’re not sure about this, start with the general .NET agent troubleshooting guide.
- If you are using the .NET Core agent in Linux, see this post instead.
You’re going to need admin privileges on your host to work through this post.
1. Start/Restart your application and check for logs.
2. Check if the .NET Core agent profiler is loaded into the application’s process
- Launch Microsoft Process Explorer as an Administrator on your host machine. (Right-click --> “Run as administrator”)
- In Process Explorer’s menu bar, select “View” --> “Lower Pane View” --> “DLLs”
- Select your application’s process in the upper pane of Process Explorer
- Look in the list of DLLs in the lower pane for an assembly called
- If you don’t see that DLL in the process, continue
- If you DO see that DLL in the process, skip down to # 4 (permissions)
3. Check for the required environment variables:
- In Process Explorer, right-click your application’s process in the upper pane and select “Properties”.
- On the screen that pops up, select the “Environment” tab.
- Make sure that all of the required environment variables are present in that window and that their values are correct.
If you don’t see all four required environment variables in that list, set your environment variables, restart your app and go back to #1.
If you DO see the required environment variables, make sure that they all have the correct values.
(see link above).
If you made any changes to your environment variables, restart your app and go back to #1
4. Check permissions.
Make sure that the user your application process is running under has read/write/execute permissions to the directory where the .NET Core agent will write its logs (
CORECLR_NEWRELIC_HOME), and all of its sub-directories.
If you made any changes, restart your app and go back to #1
If you’ve come this far and still don’t have any logs for your application you either have a compatibility issue or something out-of-the-ordinary is going on.
Contact support or ask in these forums with your specific questions.
If you have logs now
- Head back to the general .NET agent troubleshooting guide to continue.