This release is only for the Private Cloud Server and Virtual Private Cloud.
- New! Workstation monitoring now supported for Container and Native Monitoring Points—Workstation variants of the Container-based Monitoring Point (c10) and the Native Monitoring Point (n10) are now available and provide monitoring from a user workstation. These products were developed to satisfy the need to monitor network and application performance of work-from-home users. They provide 5 base application licenses and a maximum of 10 LAN and 10 WAN paths. Voice and video add-on licenses are also available.
- Enhanced Transaction Timing—A major enhancement to Experience that gives you even greater insight into the performance and behavior of your applications. The Test Timeline page and Test Drill-down page for Selenium workflows now present two timing metrics: the new Transaction Time metric (the time for the milestone to complete) complements the existing Page Load Time (the time for a page to load). You can set up alerts based on either. The primary benefits are:
- Complete visibility into all aspects of workflow execution, including easy identification of the milestones and commands that take the most time.
- Greater insight into the performance of single page applications, which use direct requests for content to the server rather than full page load requests.
Note: Requires a Monitoring Point with Selenium scripting support and at least EMP 12.7.1 software.
- Milestone Control—Alongside Enhanced Transaction Timing, you can now control the placement of milestones in your Selenium workflow. Any command can be designated as a milestone. AppNeta will continue to automatically place milestones at commands that commonly result in page requests to the web server (for example, open or *AndWait commands), but these can easily be removed if desired. Benefits of this feature include:
- Put milestones where they provide the most insight into execution of your specific workflows.
- Adopt consistent timing points across related workflows (e.g. login, submit request, logout).
Note: Related API endpoints are currently available in BETA form under /beta/webApplication.
Note: Requires a Monitoring Point with Selenium scripting support and at least EMP 12.7.1 software.
- Web path violation events now indicate milestone—Previously, web path violations identified the type of violation that occurred but did not indicate which script milestone was the source of the violation. Now, the violation event message indicates the violating milestone or shows “Overall” if the violation is not associated with any specific milestone.
- New “Add Web App Group” button—In order to simplify the workflow to create a web app group, we have added an “Add Web App Group” button to the Web Paths page.
- Disable SSL validation in HTTP monitoring workflow—In order to include cases where enforcing SSL/Certificate validation may not be desirable, we have added an “Ignore SSL Errors” checkbox in the HTTP workflow configuration within Experience monitoring. By default, we do not ignore these errors.
- New default alert profile assigned to new network paths—In order to alert you when network issues occur, we assign a default alert profile to all newly created network paths. To capture a wider variety of network issues, we have created new defaults for both data and voice networks. For data networks, the alert profile, called “Network Path Default - Data”, identifies basic data network issues that you should be aware of: connectivity loss, excessive data loss, and excessive data jitter. For voice networks, the alert profile, called “Network Path Default - Voice”, identifies basic voice network issues that you should be aware of: connectivity loss, excessive voice loss, and excessive voice jitter. The alert profile assignment can be changed or removed if required, but it ensures that there is reasonable alerting by default. See the Delivery Alerts page for information on creating and applying network path alert profiles.
- Organize your paths by location—We’ve updated the Network Paths and Web Paths pages to enable filtering, grouping, and sorting of paths based on the location of a path source or target. This provides additional flexibility in finding and grouping paths that have location attributes such as City, County, State/Province, or Country in common. In order to sort by location, you first need to select one of the location-related columns. Note that this feature requires location services to be enabled by AppNeta Support.
- Selectable interface for PathTest—Previously, when running a PathTest, you could specify the source Monitoring Point to use, but for Monitoring Points with multiple interfaces, you could not specify which interface to use. It was selected automatically. Now, the PathTest Settings pane allows you to select the source interface (Interface Address). This enables you to override the default interface and run the PathTest from the interface most relevant to your test.
- Simplified location selection—The Select Locations modal within the Application Usage Summary page has been updated to simplify interface selection. Now, non-active interfaces are separated from active ones in order to make it easier to identify and select only the active ones.
- Allow hostnames that begin with a number—Previously, we would not allow Monitoring Point hostnames that began with a number as per RFC 952. We have now eliminated this restriction as per RFC 1123.
- Simplified Add Monitoring Points workflow—We have simplified the Add Monitoring Points workflow in the APM UI. Now, all options are located under a single dropdown menu.
- Create a c50 using the APM web UI—In the previous release, the c50 Container Monitoring Point could only be created using the APM API. In this release, we have added the ability to create the c50 to the updated Add Monitoring Points workflow. Both the Azure Kubernetes (AKS) and Docker Compose deployment options are supported.
- Search for Monitoring Points by hostname and by MAC address using the API—You can now search for a specific Monitoring Point by hostname and by MAC address using the GET /v3/appliance API endpoint. To achieve this, filter parameters hostname and hardwareaddress have been added to the endpoint. This simplifies scripting logic by eliminating the need to retrieve all Monitoring Points then find a specific one within the list.
|APM-6514||Delivery||We fixed an issue where, depending on how it was created, the default UDP destination port for a dual-ended network path could be 7 rather than 3239.|
|APM-6702||Delivery||We fixed an issue where a network path was deleted but still showed up on the Network Paths page.|
|APM-7021||Delivery||We fixed an issue where traceroute data was not available and caused a “There are no Path Route records at this time” message to be displayed. In addition, the Routes pane would show no data.|
|APM-7151||Delivery||We fixed an issue where the Path Template Group page could freeze when adding a Monitoring Point.|
|APM-6701||PathTest||We fixed an issue where, if a custom port was configured in UDP PathTest, if the PathTest results were copied to the clipboard, the custom port value would not show as expected.|
|APM-7093||Voice/Video||We fixed an issue where deleting voice/video tests via the API could be quite slow.|
|APM-7383||Voice assessment||We fixed an issue where network paths were missing from the path selection list within the Voice assessment feature.|
|APM-7511||GeoMap||We fixed an issue where the GeoMap would only show path sources and targets. It would not show the network paths between the sources and targets.|
|APM-7022||Reports||We fixed an issue where Application Performance Reports were not being emailed as expected.|
|APM-7313||Reports||We fixed an issue where, when aggregating by city in the Application Performance Report, cities with the same name but in different states or countries would have their data aggregated.|
|APM-4704||Notifications||We fixed an issue that caused certain web path service quality event emails not to be sent.|
|APM-7150||Usage||We fixed an issue where the Usage > Monitoring Points page could display the message “Failed to load charts. Please try again later.” on large data sets.|
|APM-7390||User name||We fixed an issue where the user name on the top right corner of all APM pages would be distorted if the name contained an apostrophe.|
|APM-7611||API||We fixed an issue where GET /path/data API call was returning results with empty data.|
|APM-7358||Access tokens||We fixed an issue where, for SSO users with multiple roles, the New Access Token page would restrict the choice of Roles to the “lowest” role assigned (for example, “View Only”).|
|APM-7721||Security||We fixed an issue where notification profile name character limits were not being validated properly. Now, up to 255 character names are supported.|
Changes to be aware of
- Software Sequencer now called Native Monitoring Point—We have changed the name of the Software Sequencer to Native Monitoring Point in order to clarify that it is deployed to a native OS rather than to a virtual machine or to a container.
- Total Time condition changed to Page Load Time—Due to the introduction of Page Load Time, we have changed the name of the Total Time alert condition for web paths to Page Load Time. Web paths with the alert condition set prior to the name change are unaffected.
- Transaction Time now used in Comparison View and Web Dashboard—The Comparison View and Web Dashboard now present the Transaction Time metric for Browser web paths that use Selenium workflows. Legacy Monitoring Points (that do not support Selenium workflows) will continue to present the Page Load Time metric.
- Experience Monitoring Load column added to the Manage Monitoring Points page—Previously, to view the Experience Monitoring Load value, each Monitoring Point had to be selected individually to display the load value in the side panel on the Manage Monitoring Points page. Now, in order to see this metric more easily across all devices, it is also visible in a separate Experience Load column.
- Add Network Monitoring dropdown moved—We have moved the Add Network Monitoring dropdown next to the Group By dropdown on the Network Paths page.
- Capacity and utilization measurements removed from Diagnostics pages—As capacity and utilization measurements, especially for mid-path hops, could be misleading and confusing, we have removed them from the Data Details and Voice Details tabs within Diagnostics. These measurements are still available in “Advanced Mode” - accessible to users with the Advanced Diagnostics add-on privilege.
- Updates to Deep Packet Inspection Interfaces page—The Deep Packet Inspection Interfaces page has been updated to show the Monitoring Point connectivity status. In addition, the start, stop, and configure flow analysis buttons are only highlighted if they are actionable.
- HTTP monitoring support promoted from /BETA to /v3 in API—API changes implemented for HTTP Monitoring under /BETA have now been promoted to /v3. As well as adding the subCategoryType to the alertProfile endpoints, the various webApplication endpoints have been extended for HTTP monitoring to include, for example, workflowType and httpConfigurations objects.