See Service for APM system status and upgrade schedule information.
- Migrate monitoring from one Monitoring Point to another—We have added the ability to migrate monitoring from one Monitoring Point to another. The migration allows interface mapping and preserves monitoring history and (where applicable) licensing. This feature is typically used when moving to a newer Monitoring Point model, when replacing a defective Monitoring Point, or when aggregating monitoring from two or more Monitoring Points to a higher capacity replacement. As part of the migration process, the source Monitoring Point is deleted from APM.
- Retrieve licenses compatible with Monitoring Point type—We have added a filter (compatibleWithOs) to GET /v3/license that shows licenses compatible with the specified Monitoring Point type.
|APM-3914||API||We fixed an issue where the observer API was unable to send to a target using a certificate signed by Let’s Encrypt.|
|APM-3892||Experience||We fixed an issue where scrolling from the bottom to the top of the “waterfall” diagram on the Test Drill-down page would not work as expected.|
|APM-3793||Experience||We fixed an issue where there was a discrepancy between the number of web paths shown on the Overview page and those shown on the Web Paths page.|
|APM-3786||Experience||We fixed an issue where updating or deleting a web app group could take a long time.|
|APM-3456||Reports||We fixed an issue where, when scheduling a Location Bandwidth Quality Report, it was not clear that “Offices” was a required field.|