Pinning Browser Agent by Config

Related to: https://new-relic.atlassian.net/browse/NR-617347

The idea is to add a config option in your Agent to specify a specific version of the Browser Agent. You will then pass that in the Connect payload as browser_monitoring.version, which will result in getting back that version of the Browser Agent to inject. See the Agent spec for more details and the linked Feature Request for the reason behind the request. If this does not apply to your Agent, you can close this ticket.

Testing browser_monitoring.version:

• To return a js_agent_loader, you must enable browser monitoring for your test application via the UI.
  • On the side left panel -> Integrations & Agents -> Browser Monitoring -> Connect browser data to APM -> Select your application
• Not all browser agent versions are currently published to Staging, so some specific browser agent versions may not return loaders. Here is a list of versions that do/do not exist in Staging. All versions are published to Production if you choose to test there.

Search the Java agent for browser monitoring configuration and Connect payload construction, then read the linked Agent spec and feature request for the required behavior. Test with browser monitoring enabled and verify that the configured version is sent as browser_monitoring.version and produces the expected Browser Agent loader where that version is available.