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).
November 1, 2019
The Resource Performance Dashboard is enabled for any account created after the 4.5.15 release.
Version 126.96.36.19991 - October 9, 2019
- The user configuration name is changed from
userEventInfoerrors are reported to the developer console.
Version 188.8.131.5240 – August 14, 2019
The primary metric configuration allows you to set a primary metric for your browser application dashboards, summaries, and charts.
|BRUM-5318||Script set by innerHTML does not fire load event|
July 31, 2019
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.
Version 184.108.40.2061 – July 15, 2019
|BRUM-5294||JS Agent |
|BRUM-5189||No error status reported at fetch request in Ajax Event with 404 error|
Version 220.127.116.1142 - July 26, 2019
|BRUM-5369||Resource performance widget is added to dashboard even when RTA flag is disabled|
Version 18.104.22.1687 – June 18, 2019
Version 22.214.171.1241 – May 14, 2019
ResourceTimingInfo is not captured when applications are instrumented with 4.5.8 and 4.5.9 JSAgent when SPA is not set to true
April 22, 2019
Fetch Monitoring conflicts with Zone.js
Read metrics from cookies when they are not available from beacons
Increase the URL length limit in SynthPageRecordTransformer
Version 126.96.36.1998 – April 14, 2019
Deprecation and End of Life (EOL) Notices
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 188.8.131.52
- Opera 11 and older
March 25, 2019
The Browser Records by Region widget on the Browser Analyze page now enables you to zoom in to view city-level data.
|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|
Version 184.108.40.2062 – March 15, 2019
- You can now add custom user data with the
Version 4.5.7 – February 25, 2019
Version 220.127.116.110 - February 15, 2018
Business transaction correlation is now supported for Ajax requests made with the Fetch API.
Browser data will now be displayed for the 26 cantons of Switzerland in the map view of the Geo Dashboard.
Version 18.104.22.1687 - January 18, 2018
|BRUM-4743||JS Errors in iPhone Firefox when Fetch monitoring support was enabled|
Version 22.214.171.1247 - January 11, 2018
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.
Version 4.5.5 – December 21, 2018
|BRUM-4499||Updated the jackson-databind package for the Orcha utility|
|BRUM-4534||Uncaught TypeError: Cannot read property 'handleEvent' of null|
Version 126.96.36.1993 - December 7, 2018
console.erroras 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().
November 19, 2018
|BRUM-1480||The IFrame Dashboard is missing related Ajax requests|
|BRUM-4354||Custom user data date not being captured in the JSON beacon reader|
Version 188.8.131.5239 – October 15, 2018
|BRUM-4097||The README file for the EUM Server lists the wrong version|
Version 184.108.40.20647 – September 5, 2018
|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()|
Version 220.127.116.116 – August 16, 2018
July 11, 2018
The Controller is not receiving metrics because of a time skew between the Controller and the EUM Service
Child Ajax events are not reported because of missing parent page events
When an EUM app's new metric limits are reached, no new metrics are created, and data for existing metrics are not recorded