Make sure you have the web telemetry you need to detect and resolve poor user experience. This guide will help you do that by showing you how to check that you're getting the right data and that Browser is configured for you to make the most of it.
- Your web application is instrumented with New Relic Browser
- Your web application is configured for Pro + SPA
In this guide, you will check and tune the following:
- Browser application naming and sub-account placement
- JS errors
- Page views
- Distributed tracing
- Custom attributes
How's your naming and data organization?
- Web application instrumentation from different environments (dev/qa/production) should report into different Browser applications.
- Developers, operations, and product owners can work out the following using sub-account names and Browser application names:
- Which environment a Browser application supports (Such as Dev, QA, and production environments).
- The purpose of a Browser application (customer facing, internal facing, website, website component, region or regions, etc).
Need to make a change?
- You can change the name of your browser application following the renaming guide
- Making sure the Browser agent is places in the
<HEAD/>tag of your pages. You can use Chrome developer tools to verify this.
- Following these instructions for missing AngularJS errors.
- Checking to see if your site uses an error handler that’s handling errors before the Browser agent gets the chance to see them.
- Using the noticeError API to capture missing errors.
Follow these instructions to troubleshoot missing event logs.
Page URLs in the Page views UI are automatically grouped to help you manage page performance better. The algorithm that determines the automatic grouping runs when your web app is instrumented for the first time. If your web traffic today is much different from when the app was first instrumented, you may be seeing too few groups.
Use Segment allow lists to tune how your page view URLs are being grouped.
AJAX calls are grouped to make it is easier to navigate them at scale. Sometimes there are so many AJAX calls that navigating them by individual request URL is too cumbersome. Follow these steps to check whether or not you need to adjust AJAX grouping.
Use Segment allow lists to tune how your AJAX Requests are being grouped.
Distributed tracing in Browser helps you improve AJAX performance by tracing requests to the backend all the way to the final endpoint. Tracing information is useful for understanding which applications are impacting user experience. You can use this information to address services issues yourself or delegate to the team responsible.
Use NerdGraph to track changes in your web application so you can see the impact of change against performance KPIs, conversions, and user engagement.
Use custom attributes to filter and group data. Custom attributes are optional but provide a lot of value. Below are the most commonly recommended attributes. Many customers add more.
Following the steps in this guide ensures that your team is getting maximum value from New Relic Browser. It ensures you are:
- Getting the most value from the data you're collecting
- Seeing opportunities to optimize
- Able to quickly triage and troubleshoot
- Getting the data you need to create real-time business KPI dashboards