This sponsored post features a product relevant to our readers while meeting our editorial guidelines for being objective and educational.
New Relic is a performance monitoring service which runs with a variety of server and language technologies and Browser runs its analysis on your users' own computers and devices in their browsers. In doing so, it gives you a picture of your actual users' experience with your product. New Relic Browser is the only monitoring product that does this.
New Relic Browser monitors full page life cycle data—well beyond the initial page load. For each end user page load, New Relic captures:
- Time spent in the front end (browser)
- Time spent in the back end (network and web app)
- Geographic origin
- Browser type and version, and operating system
You can view the data globally across all users and see it sliced and diced by webpage, browser, user session, and location.
Browser can help you identify client-side problems that no other monitoring service can. And, it can help you identify and isolate problems with specific browsers, versions or geographic network locations. In fact, the New Relic team wrote a blog post about the crazy things it uncovered about end users' browsers during beta testing, such as malware installations and quirky Chrome behavior.
To get started, you'll need to register for your free account at New Relic:
If you're already using New Relic, perhaps from our other tutorial about WordPress and W3 Total Cache, you may need to activate the Browser Pro tutorial. Sign in and look for the "add me to the Browser Pro trial" button. This will activate the 30 day free trial for the Browser Pro features.
Once you've completed registration, follow the installation instructions on the page appropriate for your registration. I'm using Ubuntu 14.04. New Relic offers advanced installation instructions for most languages.
For my Ubuntu installation, it goes like this. The WordPress W3TC New Relic installation works a bit differently.
Add the New Relic apt repository:
echo deb http://apt.newrelic.com/debian/ newrelic non-free >> /etc/apt/sources.list.d/newrelic.list
Trust the New Relic GPG key:
wget -O - http://download.newrelic.com/548C16BF.gpg | sudo apt-key add -
Update and local package list and install New Relic:
sudo apt-get update
If you're using the standard New Relic setup, it will be:
apt-get install newrelic-sysmond
Configure and launch the system monitor. If you're using the generic New Relic setup, do this:
nrsysmond-config --set license_key=your-license-key-goes-here
Start the New Relic daemon:
Whichever approach you use, restart your web server:
service apache2 reload
After a few minutes, you should see the red message on the setup page indicating that data is flowing into New Relic from your server. Cool, huh?
After this, you can setup New Relic Browser. There are two ways to go about doing this:
- You can install the application via an APM agent on the back end and then enable the pro trial from within the app.
Both of these options are documented here.
Learning from Browser
Visit the Browser product page to see the data it collects. Navigating the Browser app is quite simple using the left side dashboard. I'm showing it below because I've omitted it from the screenshots that follow (to provide more screen real estate for the content).
The overview is the main high level view for Browser giving you a birds-eye view of performance issues that may or may not be occurring. The overview is a great place to find issues that deserve deeper inspection.
It's essentially a real time view of actual page visits, breaking down performance by time spent in the network, web server, DOM processing and page rendering.
The Apdex score gives you a quantitative measurement of the usability experiences of your site based on response time i.e. the ratio of satisfactory response times to unsatisfactory response times).
In the Overview, you can click on any item that appears to be performing poorly. Read more about using the Overview page.
Session traces give you visibility into the entire lifecycle of a web page including user interactions, asset loading, iframes, time spent waiting for Ajax calls, errors and more - tracking the real experience of a real user from start to finish.
Not only do traces identify problems - but they can show you what the user did before and after the error occurred.
Session traces help you understand:
- How users experience your page load, including time to DOM load, time waiting for Ajax requests to complete, and the user's interactions with the page
- How the New Relic metrics reflect your end users' experiences
- Where bottlenecks occur, and what may be causing them
- Why one page load may be slower than others, by providing the context for individual events during a session
Click on any page and you get a detailed breakdown of activity in any particular user's page visit. It's pretty amazing actually - and super helpful for diagnosing trouble.
Page Views shows you detailed performance by the most frequently accessed pages on your site:
When you drill down, you can see performance of the individual files being loaded by your site:
The Ajax page allows you to see what's happening with any interactive calls that you have on the page helping identify problems with your users' experience when you have time-consuming or failing calls:
Note that Browser does not automatically record Ajax data. You need to turn it on per app in the New Relic settings area. Read more about the Ajax dashboard.
New Relic Browser also lets you see the performance of your website across different browsers.
The Geography dashboard shows you performance scores of end users' actual experience from around the world. You can select specific geographic regions, such as countries or states, and then you can drill down to detailed information about page load performance and historical performance.
This can be very helpful in identifying otherwise difficult to discover network problems. Read more about using the Geography dashboard.
I hope you've found this overview to be intriguing. New Relic Browser brings some very powerful and sophisticated analysis and debugging tools to everyone's fingertips.
The New Relic Browser Pro Trial last for 30 days. While you can use the New Relic Browser lite monitoring service for free (and is included with all New Relic APM packages), you'll need to upgrade to the Pro plan (starting at $99/month for 500,000 page views) to keep the Browser service. It's also important to occasionally update New Relic and check on its log files. Review the New Relic maintenance guide.
Subscribe below and we’ll send you a weekly email summary of all new Code tutorials. Never miss out on learning about the next big thing.Update me weekly
Envato Tuts+ tutorials are translated into other languages by our community members—you can be involved too!Translate this post