With the .NET agent, you can add New Relic Browser instrumentation to your webpages. Before you use Browser with your .NET agent, refer to the .NET agent release notes, and make sure you have the installed the latest .NET agent release.
This feature is not available for asp.net core applications whether they are monitored by the .NET Framework or Core agent.
text/html and also has
<head> tag within the page.
HttpModule that modifies the page using HTTP response filters before streaming the content to the user.
The first time you enable auto-instrumentation, you may need to clean your
asp.net cache directory so that aspx pages are recompiled. Use the following command:
With this injection, previously functioning pages may stop working if a
content-type is not set correctly. To correct, review and update the
content-types in your app or disable auto-instrumentation.
A known issue in the .NET Framework agent version 22.214.171.124 prevents auto-injection in certain specific cases. This issue only affects WebForms websites running in integrated pipeline mode, and it only occurs when navigating to the website's root URL.
Manual instrumentation via agent API
If you cannot enable auto-instrumentation, you can still include the Browser agent manually by using the New Relic .NET agent API and including appropriate code in your pages.
To download the
NewRelic.Api.agent.dll, re-run the installation and reference the
- From the New Relic .NET agent directory, select the New Relic.Net agent section, then select API Assembly.
- NuGet: Install and reference the .dll by running
- To set up your web application to call the New Relic .NET agent API, add a reference to NewRelic.Api.Agent.dll to your project.
- Optional: If you are modifying the deployed application directory on the web server, copy NewRelic.Api.Agent.dll into the application's bin directory.
- Call the API in your
<head>tag. If a meta-tag with the
X-UA-COMPATIBLE http-equivattribute exists, set it after that meta tag.
- .NET Web Forms view engine
When using .NET Web Forms view engine, be sure to use
If you are using .NET ASP Web Forms with master pages, add the header manually by calling
GetBrowserTimingHeader()in your master page under the
<%= NewRelic.Api.Agent.NewRelic.GetBrowserTimingHeader() %>
Import the namespace with:
<%@ Import Namespace="NewRelic.Api.Agent" %>
- Other view engines such as Razor
<!DOCTYPE html> <html lang="en"> <head> @Html.Raw(NewRelic.Api.Agent.NewRelic.GetBrowserTimingHeader()) ... </head> </html>
- .NET MVC
When using .NET MVC, call the
To disable instrumentation:
- Disable auto-instrumentation
To fully disable auto-instrumentation, edit newrelic.config and set the
autoInstrumentflag to false:
<!-- disable auto instrumentation --> <browserMonitoring autoInstrument="false"/>
If you change the flag or uninstall the .NET agent, be sure to flush your cache again so that references to the agent are removed from compiled files.
- Disable auto-instrumentation on a particular view
To disable only auto-instrumentation on a particular view, use the agent API call
DisableBrowserMonitoring(). Add this call in any view where Browser scripts are not needed or wanted. Put this API call as close as possible to the top of the view where you want it disabled.
- Disable both automatic and manual instrumentation on a particular view
To disable both auto-instrumentation and manual instrumentation for individual webpages, use the agent API call
Follow the troubleshooting procedures if you are unable to view any Browser timing data.