You are probably reading this because you found a reference to this URL in the header of a page monitored by New Relic’s Browser product and you’re wondering what it’s all about. Let’s take a look at this URL and how Browser Monitoring works in New Relic.
If you don’t already have a New Relic account, you can get full access for free.
So what is bam.nr-data.net?
Here’s the short explanation: The Browser application monitoring agent transmits data to New Relic’s data collection servers via the domain bam.nr-data.net. Of course, there’s more to the story than that. If you’re the kind of person that needs to know more, then read on!
How does New Relic Browser monitoring work?
Depending on your subscription level, New Relic Browser can monitor a variety of details about everything from page load timing to time spent in the front end, time spent in the back end, geography, and browser type.
To collect the data, New Relic Browser uses JavaScript elements pasted or injected into your webpages, typically as part of the HEAD of the page, containing configuration details and essential browser environment instrumentation. Once the page finishes loading, an additional script is downloaded from a CDN server. This additional script processes collected data and reports it back to New Relic via bam.nr-data.net so that you can see the data in your New Relic account. You can find more details about how Browser instrumentation works in the documentation.
You should also know that New Relic Browser only collects performance data, as explained in this document. It does not collect any data used or stored by the monitored application unless you explicitly configure it to do so.
Learn more
What to deep dive into the BAM collector, check out this follow-up Level-Up Solution Relic Solution: Understanding Bam.nr-data.net, Data transmission & its Endpoints
Ready to learn more? You can review the full suite of documentation for Browser or check out New Relic University’s self-guided course.