Troubleshooting session trace collection

Problem

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

Solution

If your application is instrumented with APM and other features associated with the Pro browser agent are working, 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.
• The RUM response (very first agent request to bam.nr-data.net) returns a st OR sts flag of 0.
• Session traces isn't enabled. Check the application settings page to ensure that you've enabled session traces and have made adjustments to your sample rates.