See the service status page for AppNeta Performance Manager system status information.
- Network change events added—We now automatically detect changes to the sequence of networks (BGP Autonomous Systems) on the path between a source and a target, enabling you to detect potential routing problems or network instability. This feature is always enabled with results appearing on the Event Distribution page and in the Events chart. You can also enable notifications for Network Change events.
- PAC file support added—We now support the use of Proxy Auto-Config (PAC) files for proxy configuration. All network paths and web paths from a Monitoring Point that uses a PAC file follow its proxy definitions. This feature can be configured in the APM UI when creating or editing a web app group. It can also be configured using the /v3/webApplication APM API endpoint. The feature requires EMP 12.2.0 or later software on your Monitoring Points.
- Easier to access web proxy settings—We have moved the web proxy settings within the web app group configuration so that you no longer have to drill down through an Edit menu. You can now access the Edit Proxy Settings dialog when you configure the source Monitoring Point during web app group creation or edit.
- “Proxy Type” filter added—We have added the ability to filter by “Proxy Type” to the Web Paths page. In addition, the “Proxy Type” column is also available on the page and web paths can be sorted by this column.
- Configurable web path timeout period—You can now reduce the web path timeout period so that if a timeout does occur the delay before running subsequent scripts is reduced. The timeout can be configured during web app group creation or edit. It can also be configured in the APM API using the WebPathConfig object in the /v3/webApplication endpoint. The minimum timeout period is 25 seconds.
- Customizable columns on Web Paths page—The Web Paths page has been enhanced to include customizable columns like the Network Paths page.
- Resolved IP address in Test drill-down—We have updated the Test Drill-down page to include the resolved IP address for each milestone. This is useful when trying to determine if a specific server is impacting performance.
- Custom labels for corporate networks—We have added the ability to provide a corporate network name so that it shows up on the Route Visualization on the Network Paths page. By default, the organization name is available for display but an Organization Admin can change the label by updating the Corporate Network field on the Configure an Organization page.
- Double-click to expand networks—We have simplified the way you expand a network in the Route Visualization on the Network Paths page. Within the Network view, you can now double-click a network icon to show all hops within the network. The expand icon () also performs the same function, as in previous releases.
- Helpful links from “Too many paths” error message—We have updated the “Too many paths” error message on the Route Visualization to provide helpful filter links if you are viewing more than 20 network paths. The links are for filtering by Network Path Name, Monitoring Point, and Target.
- View all event integrations—You are now able to use the GET /observer/ endpoint to view all event integrations, not just those created by your user ID. This capability is only available to users with the “Organization Admin” role using the allUsers=true parameter. You will see the event integration information for users you have access to.
- New applications supported—The Usage Monitoring classification library has been updated with new applications including:
- HBO Nordic
- Elisa Viihde
- Yle Areena
- Application improvements—Application classification improvements have also been made to applications including:
|APM-3081||Usage charts||We fixed an issue where Usage data was not being rolled up properly for r90 and r1000 Monitoring Points. The symptom was that Usage chart data could look different depending on when you accessed the charts.|
|APM-2954||API||We fixed an issue where clear events were not being sent by the observer API.|
|APM-2805||Path template groups||We fixed an issue where the Path Template Groups feature was not updating all changed path properties as expected.|
|APM-2689||Packet capture||We fixed an issue where packet capture passphrases that contained special characters rendered the captures irretrievable.|
|APM-1609||Network Paths||We fixed an issue where the column header configuration on the Network Paths page was lost when navigating between Organizations.|
|APM-686||Reports||We fixed an issue where the link at the top of the Experience Detail report (emailed or scheduled version of the report) pointed to the Network Paths page rather than the Experience Test Timeline page.|
Changes to be aware of
- Route Visual name change—We have changed the name of the Route Visual pane to Routes. We have also changed the labelling. What was labelled Date & Time is now labelled Center Time. If a date and time is specified, it is located in the center of the time range.
- Route Visual time range behavior change—We have changed how we remember the time range. Previously, we always remembered the last selected time range. In order to improve performance, we now reset the time range to 10 minutes whenever the Center Time or search query are changed.
- Route Visual incomplete traceroute handling—We have changed how we indicate incomplete traceroutes. Terminated traceroutes are indicated either by a red circle around a hop, or by a red target. In addition, the number of traceroutes that terminate at a hop or target are indicated in the data bar when the object is hovered over or clicked.