Skip to end of metadata
Go to start of metadata

On this page:

Related pages:

Your Rating:
Results:
1 Star2 Star3 Star4 Star5 Star
6 rates
The following notes describe 4.5.x updates to IoT Monitoring.

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).

The most recent releases appear at the top of the page.

4.5.17 Updates

January 10, 2020

Enhancements

You can now create custom geo-mapping files to map internal IP addresses to geolocations for your IoT applications, enabling you to monitor the performance of devices running in Virtual Private Clouds (VPCs) with internal addresses that are distributed across different geographies.

4.5.8 Updates

March 25, 2019

Enhancements

You can now use the Widget Builder to build custom Geo widgets based by using the Geo graph type. You can build geo widgets for any of the IoT dashboards to view data at the country, region, and city level. See Build Custom Dashboard Widgets to learn how to create custom widgets and Choose the Best Graph Type to learn more about the Geo graph type.

Resolved Issues
Key
Summary
EUMIOT‑1336

Slow download of EUM metrics are causing EUM metrics to be dropped

4.5.4 Updates

October 19, 2018

Enhancements

IoT Monitoring now includes geo data that is determined by resolving the IP address calling the IoT REST API. You can view the country, region, and city for devices in the Unique Devices widget on the Devices Dashboard. You can also use the Widget Builder to create widgets based on the geo data.

4.5.2 Updates

October 15, 2018

IoT Monitoring UI

Enhancements

Performance improvements were made in the rendering of IoT data in the Controller UI. The Connected Devices tab, the Errors Dashboard, and the Network Request Dashboard now load significantly faster.

4.5.1 Updates

Version 4.5.1.24339 – September 4, 2018

IoT REST API

Enhancements 

  • The IoT REST API now enables you to accept new runtime values for the StackTrace object. In addition to "java" and "native", you can now also set the runtime values "python", "javascript", ".net", and "node.js". If the runtime field is populated with an unsupported language, then the event in the beacon will be marked with a validation error. See the IoT REST API documentation for more information.

4.5.0 Updates

July 11, 2018

Enhancements