See the service status page for AppNeta Performance Manager system status information.
- Improved API security with API Access Tokens—Previously, you required Basic Authentication (username and password) to access the API. Now, you can also use API Access Tokens. API Access Tokens provide better security because username and password do not need to be encoded into scripts or applications that access the API. In addition, the authentication token does not carry any user information.
- Additional location aggregation options now available on Application Performance Report—Previously, network paths were aggregated in the Application Performance Report by the “most specific” information identified in the source Monitoring Point’s location configuration. It used the following order of preference: City, State/Province, Country, formatted text address, Monitoring Point name. You now have the ability to specify the aggregation method and aggregate by Monitoring Point, City, State/Province, Country, or Most Specific.
- Improved web path selection in Web Dashboards—To speed up the selection of web paths when creating a Web Dashboard, we now provide the ability to check and uncheck individual web paths or all web paths in a web app group.
- Delete users via the API—We have added the DELETE /v3/user API endpoint to provide the ability to delete users. Note that this capability is only available to Organization Admin users.
|APM-6230||Experience||We fixed an issue where some drill-down charts prior to March 9, 2020 may report a time different than the End User Experience and Milestone Breakdown charts.|
|APM-6128||Reports||We fixed an issue where the Application Performance Detail Report could display network paths that were not in any of the saved lists used by the report.|
|APM-6056||Observer API||We fixed an issue where events could stop being sent to the event integration server.|
|APM-5884||Monitoring Migration||We fixed an issue where, when migrating monitoring from one Monitoring Point to another, data from the primary Usage interface on the source Monitoring Point could be moved to a secondary Usage interface on the replacement Monitoring Point rather than to its primary Usage interface.|
|APM-5697||Notifications||We fixed an issue where notifications were sent for network paths but were only enabled for web paths.|