After generating traffic and waiting five minutes, you do not see any browser monitoring data for your .NET app.
To troubleshoot missing data:
Make sure you have installed the latest release of the .NET agent.
Follow the troubleshooting procedures for missing data as applicable.
Verify whether your pages are rendered using ASPs. If you use another rendering technology, use manual instrumentation.
Flush your .NET cache.
<head>tag of your pages to render on the server.
Verify that your agent is configured to auto-instrument pages. Edit
newrelic.configand verify that
autoInstrumentis set to
Check whether IIS page compression is disabled. If compressed before the .NET agent attempts browser instrumentation, the necessary
<HEAD>tag won't be found. For instructions on how to check that, see Microsoft documentation.
Look at the source of one of your pages through a browser. Look for a script with references to
Here are some additional troubleshooting tips:
Additional troubleshooting tips for .NET agent
IIS exception error
With IIS, you may receive an
To solve this problem, you must manually implement the browser agent: Set
Razor framework error
With the Razor framework, you may encounter the following message:
To solve this problem, follow the browser troubleshooting procedures for Razor frameworks.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.