When the New Relic Browser team heard we were planning to embed analytics into all our products, we were inspired! We were excited to support the initiative right away with the revamp of our Geo Analytics feature (now in private beta).


france chart


Geo Analytics offers a curated view in New Relic Browser, designed to help make it easy for our users to understand how Web user experience varies across browser characteristics, as well as by geography, whether drilling down from country to state, city, and even zip code based on network attributes.* By segmenting their customers’ experience according to browser and geography, developers, application owners, and operations teams can devote their attention where it’s needed most.

PageView events in New Relic Insights

But we did a lot more. As we brainstormed how to provide additional value to our users, we quickly zeroed in on a key advantage of our client-side positioning: we have a uniquely detailed view into network performance metrics that our server-side counterparts don’t, by splitting out overall application speed into frontend, network, and backend components.

So today we are excited to announce that PageView events in New Relic Insights now include the following network-related attributes by default whenever users visit your application from a supported browser:

  • Autonomous System Network (ASN)
  • Autonomous System Network (ASN) Organization
  • ASN Latitude
  • ASN Longitude
  • Connection Setup Duration
  • DNS Lookup Duration
  • Network Duration
  • Secure Handshake Duration


Pageview attributes


Think of the possibilities!

  • Query the traffic from a specific state and find out which ASN Organizations result in the longest Connection Setup Durations and Network Durations. Time to look at a peering agreement!
  • Were last night’s unusually long page load durations caused by your client-side code, or did an ASN Organization have a deprecation of service?

Answers to all questions like these are now just a lightning fast NRQL query away.

We didn’t stop there though! To establish parity between New Relic Insights PageView and the page-load performance charts in the New Relic Browser UI, we added the following default PageView attributes:

  • Device Type
  • DOM Processing Duration
  • Page Rendering Duration
  • Queue Duration

Now, with existing and new attributes you can use New Relic Insights to build custom views into your page load performance in a way that matches what you see in the New Relic Browser UI. This is particularly useful for those doing analytical deep dives, companies that use New Relic Insights for wall-mounted office monitors, and for users building Data Apps to serve their colleagues who don’t need direct access to New Relic Browser or New Relic Insights query capabilities.

All of the above attributes are available in New Relic Insights today—there is nothing you need to do but start using them. For example, below you can see the new, visual Insights Data Explorer showing DNS Lookup Duration (a new attribute), faceted by City, and filtering for Mozilla user agents on Linux. This is just one of numerous types of analyses that you can do to inform the location of frontend performance problems.


New Relic Insights Data Explorer 11 no NRQL

[click to enlarge]

Note that some attributes are dependent on the Navigation Timing API that is included in most modern browsers. It’s unlikely that all of your traffic will come from supported browsers, so we’ll leave those attributes empty on events from unsupported browsers. As of this writing, our internal data shows that 89% of events from applications monitored by New Relic are capable of reporting these new metrics, but YMMV (your mileage may vary).

Head on over to New Relic Insights to get started, or visit docs.newrelic.com for more details on these exciting new attributes.

Al Sargent contributed to this post.


*A note about Geography and Networks: When we talk about geography and location above, we mean the latitude and longitude of the postal code where the Autonomous System Network (ASN) is registered, which can vary significantly from a user’s actual location. What does this mean? When someone uses a Web app, the packets from their HTTP requests appear on the Internet when they leave the ASN. An ASN can be thought of (more or less) as an Internet Service Provider. So, if your ASN connects to the Internet far away from your actual location, the PageView attributes will reflect the ASN’s postal code, not your location.


Globe image courtesy of Shutterstock.com.

Jeff Martens is a Portland-based Product Manager, leading the New Relic Browser offering. Prior to his role on the New Relic Browser team, he served as a Product Manager for New Relic Insights. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!