See Service for AppNeta Performance Manager system status and upgrade schedule information.
- “Path Template Group” filter added—We have added the ability to filter and group by “Path Template Group” to the Network Paths page. In addition, the “Path Template Group” column is also available on the page and network paths can be sorted by this column.
- Convenient access to create Path Template Group page—We have replaced the “+ Network Path” button on the Delivery > Network Paths page and the Dashboards > Overview page with a dropdown that provides options to create a Network Path or a Path Template Group.
- “Importance” property now included in Service Quality events—We now include an “Importance” property in SQA_EVENTs returned by the APM Event Integration feature.
|APM-4863||Delivery||We fixed an issue where the search function on the Network Paths page was unable to find some network paths by PathID or Name.|
|APM-3935||Delivery||We fixed an issue on the Route Visualization where traceroutes originating from multiple predecessor networks to a common downstream network could overlap and only be seen when the downstream network was expanded.|
|APM-1628||Delivery||We fixed an issue where network path groups displayed on the Network Paths page using the Grouped By view could overlap one another.|
|APM-4813||Diagnostics||We fixed an issue where, for dual-ended paths, inbound diagnostics could be linked to outbound diagnostics resulting in odd and unexpected hop ordering.|
|APM-5035||Monitoring Point||We fixed an issue where Monitoring Points could show as online on the Manage Monitoring Points page even though they were offline.|
|APM-1170||Monitoring Point||We fixed an issue where the Manage Monitoring Points page could show a private IP address in its Public IP Address field.|
|APM-5110||API||We fixed an issue where the GET /v3/traceroute API endpoint could return an unexpected 500: Internal Server Error.|
Changes to be aware of
- Change to representation of repeated hops on Route Visualization—A given hop can show up more than once on a traceroute for various reasons, including when tunnel (GRE) interfaces terminate on an interface and when NAT is performed at an interface. Previously, we counted these as separate hops and indicated it as a small loop on the Route Visualization visual. This was confusing and was interpreted as a routing loop. Now, the hop is only counted once and the loop is removed from the visual. The repeated hops can still be seen in the route Export.