4.5.x Browser Real User Monitoring Notes

Related pages:

The following notes describe 4.5.x updates to Browser Real User Monitoring, which includes the JavaScript Agent.

If an artifact has been updated, the version number of the updated artifact and its availability date are listed below. The version number corresponds to that shown on the download portal (http://download.appdynamics.com).

4.5.15 Updates

November 1, 2019

Enhancements

The Resource Performance Dashboard is enabled for any account created after the 4.5.15 release.

4.5.15 (JavaScript Agent) Updates

Version 4.5.15.2691 - October 9, 2019

Enhancements

The user configuration name is changed from angular to isZonePromise.
userEventInfo errors are reported to the developer console.

4.5.13 (JavaScript Agent) Updates

Version 4.5.13.2640 – August 14, 2019

Enhancements

The primary metric configuration allows you to set a primary metric for your browser application dashboards, summaries, and charts.

Resolved Issues

Key	Summary
BRUM-5318	Script set by innerHTML does not fire load event

4.5.12 Updates

July 31, 2019

Enhancements

The Resource Performance Dashboard gives you a high-level overview of how your resources affect the performance of your browser application. You can use this dashboard to pinpoint resource-related performance issues affecting the user experience.

4.5.12 (JavaScript Agent) Updates

Version 4.5.12.2461 – July 15, 2019

Resolved Issues

Key	Summary
BRUM-5294	JS Agent `window.onerror` TypeError causes Firefox Crash
BRUM-5189	No error status reported at fetch request in Ajax Event with 404 error

4.5.11 Updates

Version 4.5.11.3842 - July 26, 2019

Key	Summary
BRUM-5369	Resource performance widget is added to dashboard even when RTA flag is disabled

4.5.11 (JavaScript Agent) Updates

Version 4.5.11.2347 – June 18, 2019

Enhancements

It is recommended but no longer required to load the JavaScript Agent before Angular for Fetch API support. See Fetch API support for SPA2 Monitoring.

4.5.10 (JavaScript Agent) Updates

Version 4.5.10.2271 – May 14, 2019

Resolved Issues

Key	Summary
BRUM-5122	ResourceTimingInfo is not captured when applications are instrumented with 4.5.8 and 4.5.9 JSAgent when SPA is not set to true

4.5.9 Updates

April 22, 2019

Resolved Issues

Key	Summary
BRUM-4744	Fetch Monitoring conflicts with Zone.js
BRUM-4950	Read metrics from cookies when they are not available from beacons
BRUM-4978	Increase the URL length limit in SynthPageRecordTransformer

4.5.9 (JavaScript Agent) Updates

Version 4.5.9.2098 – April 14, 2019

Enhancements

The JavaScript Agent now supports the monitoring of Fetch API calls in Angular.js and Angular 2–5 applications.

Deprecation and End of Life (EOL) Notices

The JavaScript Agent will no longer be tested and certified to collect and report data on some older browsers due to the very low usage of those older browsers. The JavaScript Agent instead will support more current browsers by default.

Monitoring and reporting on the following browser versions will be disabled by default and no longer certified:

IE9 and older
Safari 3 and older
Chrome 1.0.154.59
Opera 11 and older

You can still enable monitoring for older browsers through the configuration of the JavaScript Agent. Note that this configuration will continue but not certify the compatibility with older browsers.

4.5.8 Updates

March 25, 2019

Enhancements

The Browser Records by Region widget on the Browser Analyze page now enables you to zoom in to view city-level data.

Resolved Issues

Key	Summary
BRUM-4924	Correct BT Correlation for Fetch API calls by changing the ADRUM headers from "isAjax: true" to "isAjax:true"
BRUM-4634	Excluding a page type from "Pages and AJAX Requests" excludes all other page types with the same page name

4.5.8 (JavaScript Agent) Updates

Version 4.5.8.2022 – March 15, 2019

Enhancements

You can now add custom user data with the userEventInfo object for Ajax calls made through the Fetch API. See Ajax Requests Using the Fetch API for an example of how to configure the JavaScript Agent to match request URLs and capture request body parameters.
You can configure the JavaScript Agent so that the resource timing buffer for single-page applications is not cleared to capture resource timing data. For implementation details, see Disable the Clearing of the Resource Timing Buffer for SPAs.

4.5.7 Updates

Version 4.5.7 – February 25, 2019

Resolved Issues

Key	Summary
BRUM-4752	JavaScript Agent versions 4.5.5+ throw a JavaScript error when using the Ajax API

4.5.7 (JavaScript Agent) Updates

Version 4.5.7.1910 - February 15, 2018

Enhancements

Business transaction correlation is now supported for Ajax requests made with the Fetch API.

4.5.6 Updates

Geo Dashboard

Browser data will now be displayed for the 26 cantons of Switzerland in the map view of the Geo Dashboard.

4.5.6 (JavaScript Agent) Updates

Version 4.5.6.1837 - January 18, 2018

Resolved Issues

Key	Summary
BRUM-4743	JS Errors in iPhone Firefox when Fetch monitoring support was enabled

Version 4.5.6.1817 - January 11, 2018

The JavaScript Agent now supports, by default, the monitoring of Ajax requests made through the Fetch API. The Fetch API calls will be treated and displayed as Ajax requests in the Controller UI.

You can include and exclude as well as set call limits per page for Fetch API calls just as you would do with typical XHR calls. Correlating business transactions and reporting custom data for Fetch API calls, however, are not supported yet. To disable the monitoring of Fetch API calls, see Disable Monitoring of Fetch API Calls.

4.5.5 Updates

Version 4.5.5 – December 21, 2018

Resolved Issues

Key	Summary
BRUM-4499	Updated the jackson-databind package for the Orcha utility
BRUM-4534	Uncaught TypeError: Cannot read property 'handleEvent' of null

4.5.5 (JavaScript Agent) Updates

Version 4.5.5.1663 - December 7, 2018

Enhancements

The JavaScript Agent can use the request body attached to Ajax requests to set custom user data. To capture the request body, the JavaScript Agent must be configured to match the Ajax URL or the HTTP method used to make the Ajax request.
The JavaScript Agent captures error messages from single-page applications that were sent only using console.error as well as capture error events with a DOM Level 2 listener instead of using window.onerror, so you don't need to use the ADRUM.listenForErrors().

4.5.4 Updates

November 19, 2018

Resolved Issues

Key	Summary
BRUM-1480	The IFrame Dashboard is missing related Ajax requests
BRUM-4354	Custom user data date not being captured in the JSON beacon reader

4.5.2 Updates

Version 4.5.2.25039 – October 15, 2018

Resolved Issues

Key	Summary
BRUM-4097	The README file for the EUM Server lists the wrong version

4.5.1 Updates

Version 4.5.1.24447 – September 5, 2018

Resolved Issues

Key	Summary
BRUM‑3742	PLT value high due to the counter mismatch in observers
BRUM-3855	removeEventListener() no longer works after the listener is wrapped by Causality.wrap()

4.5.1 (JavaScript Agent) Updates

Version 4.5.1.1066 – August 16, 2018

Enhancements

You can now limit which virtual pages are monitored by defining filters in the JavaScript Agent configuration. See Exclude Virtual Pages from Being Monitored to learn how to define filters and set the JavaScript Agent configuration.

4.5.0 Updates

July 11, 2018

Enhancements

SPA2 Monitoring now enables you to use the JavaScript API to manually report events and name virtual pages.
Browser RUM Analyze now displays request details in the Session Details dialog and has filters for viewing requests that have resource timing metrics or by the record types Page & Ajax Loads or Post-Load JavaScript Errors.

Resolved Issues

Key	Summary
BRUM‑3808	The JavaScript Agent component that monitors and reports Ajax events conflicts with zone.js
BRUM-3734	The Controller is not receiving metrics because of a time skew between the Controller and the EUM Service
BRUM-3615	Child Ajax events are not reported because of missing parent page events
BRUM-3571	When an EUM app's new metric limits are reached, no new metrics are created, and data for existing metrics are not recorded
BRUM-3551	The JavaScript Agent is freezing a single-page application when the application triggers a search event