On this page:
On this page:
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).
Version 126.96.36.1992 – March 15, 2019
You can now add custom user data with the
Version 4.5.7 – February 25, 2019
Version 188.8.131.520 - 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 184.108.40.2067 - 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 220.127.116.116 - December 19, 2018
|BRUM-4616||JS Agent: adrum-18.104.22.1683.js is throwing JS error|
Version 22.214.171.1243 - 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 126.96.36.19939 – October 15, 2018
|BRUM-4097||The README file for the EUM Server lists the wrong version|
Version 188.8.131.5247 – 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 184.108.40.2066 – 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