This project will allow users to inject the NR Browser Agent into tabs in Chrome and Firefox using a browser extension for testing, debugging, and demos. Different versions of the agent will be accessible and configurations will be able to be made on the fly.

1. Download this repository by clicking Code > Download ZIP on the main page.
2. In Chrome, navigate to chrome://extensions and skip to step 5 or select the Settings Menu in the top right corner
3. Select More Tools
4. Choose Extensions
5. Enable Developer Mode in the top right corner
6. Click the Load Unpacked button, and select the folder holding the extension files downloaded.

1. Before using, please go through the Installation steps
2. Open the extension by clicking on its icon.
3. Supply the staging-one.newrelic.com NR1 account info to the extension, this is where the agent will send data.
   • Select a build of the agent (lite, pro, spa) and a version or
   • Select custom and supply a full url to the loader script and aggregator script
     • If you do not supply the aggregator script url, it will use the custom loader url to generate an aggregator url.
4. Make sure Tracking is set to On
5. Refresh the page for any changes to take effect, including to inject the NR Browser Agent and begin observing the page and any subsequent page.
   • All configurations are accessed when the page loads, any changes you make will only be valid once you've refreshed the target page
   • Use the "refresh all tabs" button to refresh all tabs in your browser
6. Open your chrome devtools and enable verbose logging to see decoded calls to NR1.

Every-time a file in the extension is updated, the extension needs to be refreshed:

• Go to chrome://extensions
• Under the extension, click on Reload (or press C-R)
• Runtime logs can be viewed in the extensions page

• Background Process: under the extension, click inspect views background page
• Popup Process: Right click the extension in the top corner of chrome, and hit inspect popup

As of right now, all data is only sent to staging-one.newrelic.com accounts. An input is planned to be added to change the beacon locations.

New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub. You can find this project's topic/threads here:

Explorers Hub

We encourage your contributions to improve nr-ba-injector-extension! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at [email protected].

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

nr-ba-injector-extension is licensed under the Apache 2.0 License.