Troubleshooting session trace collection

Problem

You're not seeing session traces for your browser application.

Solution

If your application is instrumented with New Relic APM and is correctly collecting all other Browser Pro data, follow these steps:

  1. Check if you are using multiple names for your application. Session traces are written only to the primary application.
  2. If you are using multiple names, check your APM application names to verify that the app is listed first.
  3. If the application is not listed first, look for session traces in the application name listed first instead.

Other reasons that you may not see session trace data include:

  • The end users are not using browsers that support the Resource Timing API.
  • The end users cannot post data to the /resources endpoint on bam.nr-data.net.

For more help

Additional documentation resources include:

Discuss Browser monitoring in the New Relic Online Technical Community! Troubleshoot and ask questions, or discuss JavaScript error reporting or AJAX timing in detail.

If you need additional help, get support at support.newrelic.com.