Browser Troubleshooting Framework Configuration

Once New Relic Browser agent has been installed successfully, there are few config settings that are worth checking to avoid/troubleshoot configuration related issues.

In case you are still facing any issues with installation, please refer to this Troubleshooting Browser Installation doc for more information.

  1. Placement of Browser snippet:

    New Relic Browser script has to exist inline with the code inside the segment. It cannot be configured via an externally sourced javascript file. Data might still continue to report with this setting, but this is not a recommended approach. The same has been mentioned in our product documentation linked here.

  2. Strictly no changes to the Browser snippet:

    The browser script should not be modified in any manner. It could lead to unexplained behaviour of the agent.

  3. Using the right version of Browser script:

    If the Browser agent has been installed via an APM agent, by default it activates the Lite version of the Browser script. You can change it based on your requirement and the level of information you want to monitor for your apps from the Browser UI -> Application settings page. Here you can select Pro or Pro+SPA version as per your needs.

    Once the settings are saved, the APM agent will be responsible for inserting modified versions of the script onto your web pages. However, if you are doing these changes for the copy/pasted version of Browser installations, the updated script needs to be copy/pasted again into your code.

  4. Toggle cookie collection On/Off:

    The browser agent now accepts new configuration privacy.cookies_enabled. When it is set to false (OFF), the agent doesn’t write any cookies (JSESSIONID & NREUM) and it also notifies the intake server to not return a cookie. This enables customers to comply with GDPR/PECR ICO guidelines around cookies. By default, all current and newly created applications will have this value set to true (ON), so there will be no change in the data currently being collected by the agent. Admin users must toggle the setting to OFF and redeploy the agent in order to see this change take effect.

    More details can be found here.

  5. Missing AJAX data:

    Check this document for detailed steps if you are not seeing Ajax data for your Browser application.

  6. Missing Session Traces:

    Check this document for more information regarding missing Session Traces.

  7. Enabling cross-origin resource sharing (CORS) to avoid missing stack traces for JS errors:

    JavaScript (JS) error events are compiled on the Browser monitoring JS errors page. By default, they’re grouped by error message. When you select a single error event, you’ll see more detail in its Error Instances list. In some cases, one or more of the instances may not have a stack trace. More details can be found here.

  8. Missing specific page or endpoint names in Browser URLs:

    Browser monitoring automatically learns to group your page views when your application is first deployed, and it adds that information to an allow list for URLs, but this grouping may not match your current page view information. You can manage a list of specific domains or URL segments that you always want to be seen in the URL paths. It is also possible to block if you want to block specific domain related data. This documentation has more details on these concepts.