.NET Config Install Framework
If IIS: Verify that a command line IISRESET has been performed after any changes to newrelic.config or app.config. (Log level adjustments do not require an IISRESET)
Validate the newrelic.config file against the newrelic.xsd:
- Can use xmllint depending on OS or other trusted validator
- Use the newrelic.xsd for your version, this can be found in the .NET Agent folder or in .NET agent zip file download: https://download.newrelic.com/dot_net_agent/latest_release/ look for something similar to: newrelic-agent-win-x64-8.x.x.x.zip
- If not, you’ll see errors to look for and correct. Note that if the agent version is older, such as a 6.x version, you will want to use the 6.x .xsd file to validate against, as features are added or deprecated over time.
Check precedence levels of config for conflict or unexpected settings: (Sorted in order of highest to lowest)
- web.config or app.config or appsettings.json
- Environment variables
- Server-side config
- App-local newrelic.config
- Default (global) New Relic config.
- You can make a copy of your newrelic.config and place it at the root folder of your application for app specific naming and configurations, which will take precedence over your global newrelic.config
- If you modify your newrelic.config file, make sure it defaults the default UTF-8 encoding. If your editor adds a BOM(Byte Order Mark) to encoding, the agent will be unable to read the file and will not start up in Linux.