May 19, 2021 (vPCA 14.9.1)

This release is only for the Private Cloud Server and Virtual Private Cloud.

Enhancements

  • New dashboards!—We have added five new dashboard types to help isolate poorly performing network paths and applications:
    • Network Violation Summary - This dashboard provides an easy way to identify and investigate network path violations.
    • Web App Violation Summary - This dashboard provides an easy way to identify and investigate web path violations.
    • Current Network Violation Map - This dashboard provides a geographical view of your network status. It includes the powerful network path filtering that’s also available on the Network Paths page.
    • Web App Performance - This dashboard provides the status of selected web app groups over time (up to 30 days).
    • Application Quality - This dashboard enables you to view the performance of the network and web paths that deliver an application over time (up to 30 days). It provides a quick way to find the worst performing areas of your network.
  • New dashboard management functionality!—We have made significant enhancements to the dashboard functionality by providing the ability to manage the list of dashboards. Enhancements include:
    • the ability to create and name dashboards of a given type.
    • the ability to delete dashboards.
    • the ability to manage the dashboards list by specifying a “home” dashboard and moving a dashboard to the top of the list.
    • the ability to share a link to a dashboard.
  • Significant improvements to the Monitoring Points page—In order to make it easier to select the Monitoring Points you need to manage, we have enhanced the Monitoring Points page with the ability to search for and filter Monitoring Points in the same way you can search for and filter network paths and web paths. In addition, we have made significant speed improvements so that results are returned quickly whether you have only a few Monitoring Points or thousands. The new Monitoring Points page is currently running in parallel with the old page and can be accessed via the “Let me see!” link in the banner at the top of the old page.
  • Group network paths by ISP—We have updated the Network Paths page by providing the ability to group network paths by Internet Service Provider (ISP). This grouping enables you to compare paths on the various ISPs they traverse in order to help detect connectivity or performance issues related to a particular ISP.
  • New API endpoints for Path Template Groups—We have added two new endpoints for subscribing a Monitoring Point / interface to, or removing it from, a path template group:
    • POST /v3/pathTemplateGroup/{id}/monitoringPoint - Used to subscribe a Monitoring Point / interface to the specified path template group.
    • DELETE /v3/pathTemplateGroup/{id}/monitoringPoint/{seqId} - Used to remove a Monitoring Point / interface from the specified path template group.
  • Streamlined Web App Group creation workflow—We have reduced the number of clicks required to create a Web App Group from the Web Paths page. Also, when the process is complete, you return back to the Web Paths page rather than the Web App Groups page.
  • Easily confirm that web paths have active alert profiles—We have added a column to the Web Paths page that shows the Alert Profile applied to each web path. An important use of this new column is to confirm, at a glance, that all web paths have an Alert Profile applied to them.
  • Test completion status line for Browser workflows—We have added a test completion status line to the Transaction Time and Page Load Time charts like we have for the HTTP Response Time chart. The status line indicates when workflows complete successfully, when they don’t complete, and when the web path is not being monitored (for example, when it is disabled or unlicensed). It provides an at-a-glance view of whether there are issues with workflow completion over the selected time period.
  • Larger snapshots shown in Experience workflows—In order to provide better clarity when viewing a snapshot collected by an Experience workflow, we have increased the size of the display window when you click it. Snapshots can be seen during a workflow Preview, by using the captureEntirePageScreenshot command, or in the Snapshots section of the Test Drill-down page when you have a script error.

Resolved issues

ID Keyword Description
APM-9353 Delivery We fixed an issue where Network Paths could get stuck in a diagnostic state.
APM-9064 Voice test We fixed an issue where a Voice test could not be scheduled when “Between” was selected as the “Time of the day” option.
APM-9722 Experience We fixed an issue where an error could occur when trying to add a supplementary target while specifying a Target URL during web app group creation.
APM-9135 Experience We fixed an issue where a web path could show as “Ok” even though it was not successfully connecting to its target.
MP-3371 Usage We fixed an issue where MS-Teams traffic was not distinguished from Skype traffic. MS-Teams traffic is now identified as “Microsoft Teams” within Usage monitoring. This fix requires EMP 12.8.2 or later to be running on your Monitoring Points.
MP-3597 Usage We fixed an issue where Fuze traffic was not being categorized appropriately within Usage monitoring. This fix requires EMP 12.8.2 or later to be running on your Monitoring Points.
APM-8427 Usage We fixed an issue where Violation events re Twilio traffic were identified as WhatsApp Voice Calling traffic. This fix requires EMP 12.8.2 or later to be running on your Monitoring Points.
APM-8463 Usage We fixed an issue where Usage data could stop being displayed for a period of time after migrating a Monitoring Point.
APM-9882 Usage We fixed an issue where Saved Views in Usage were not visible to View Only and Standard users.
APM-9375 Reports We fixed an issue where the “Network and Web Path” option within the Performance Data field of the Application Quality report was not persisted when scheduling the report.
APM-9378 Reports We fixed an issue where the Application Quality Report, when scheduled, would only run using default settings - not saved settings.
APM-9371 Reports We fixed an issue where the Application Quality Report could show no monitoring data for some locations.
APM-9350 Reports We fixed an issue where connectivity violations on the Application Quality dashboard and report could also be counted as performance violations.
APM-9690 Reports We fixed an issue where the Saved Lists shown on the Application Quality report were not being displayed in alphabetical order.
APM-9425 Reports We fixed an issue where the alert threshold line did not display in the correct location on the Network Path Detail report.
APM-9723 Report We fixed an issue where the Performance Violation count on the Application Quality report was incorrect when a path was in violation for the entire reporting period and other violations occurred during that time. In this case the violation count should have been 1.
Screenshot of the path area of the Application Quality report with Performance Violations highlighted.
APM-9376 SSO We fixed an issue where users with custom roles were unable to login via Single Sign-on (SSO).
APM-9705 SSO We fixed an issue where, when attempting to sign in using Single Sign-on (SSO), you could receive a “400 - Bad Request” error.
APM-9013 Password reset We fixed an issue where the password reset page returned a 500 error and blocked password reset attempts.
APM-8728 API We fixed an issue where the GET /v3/appliance API endpoint could return a different list of localNetworkInterfaces when filtered using different parameters.
APM-8897 Monitoring Point install We fixed an issue where accessing the Windows NMP download page on APM returned a 404 error.
APM-8551 Migration We fixed an issue where Monitoring Point migration from macOS NMP 8.4.x to 12.9.x could fail with the error: “Problem with Paths Migration. Internal Server Error”.

Changes to be aware of

  • Legacy Monitoring Points going offline in next release—To harden security, we are deprecating TLS1.0/1.1 in favor of TLS1.2. In this release you have the option to block all TLS1.0 and TLS1.1 connections. In the next release, all TLS1.0 and TLS1.1 connections will be blocked. As a result, legacy Monitoring Points will be going offline. Before deploying the next APM-Private (vPCA) release, you will need to migrate all Legacy Monitoring Points (m20, m22, m30, r40, r400 and the Software Sequencer) to current generation Monitoring Points (m35, m50, m70, r90, r1000, v35, CMP, and NMP) as the older Monitoring Points only support TLS1.0/1.1. Please contact your AppNeta Customer Success representative if you have any questions or for help with a transition plan.
  • Monitoring Point hostname change behavior has changed—Previously, when a Monitoring Point’s hostname changed, it’s Monitoring Point name used by APM would change as well - to keep the two names in sync. This is still true except in the cases where the Monitoring Point name has been manually changed in APM. In these cases, if the hostname is changed, it no longer affects its Monitoring Point name in APM.
  • Renamed report—The “Application Performance” reports have been renamed as “Application Quality”.
  • Updated Application Quality report summary chart calculation—We have modified the calculation of the summary chart on the Application Quality report to be more intuitive. The summary chart is now calculated based on the state of all paths selected for the report, not based on equally weighting the aggregated status of each location. Equally weighting the locations had the effect of potentially over-representing locations with few paths and under-representing those with many paths. This same change is applicable to the Application Quality dashboard.
  • HTTP Authentication password is now masked—The HTTP Authentication password (set in Experience workflows) was previously viewable after it was saved. It now behaves like password variables and is viewable only when it is being entered, and not after it is saved.
  • Organization Site Name is now configurable—Within Manage Organizations, we now allow the Site Name to be edited after the organization is created.
  • Additional characters allowed in Custom Tags—In order to support phone numbers and email addresses as Custom Tags, we have added support for “+” and “@” characters.
  • Added filters for GET /v3/pathTemplateGroup—We have added seqid and seqGuid filters to GET /v3/pathTemplateGroup in order to filter path template groups that have a subscribed Monitoring Point with a specific ID or GUID.
  • Change to error returned in PATCH (or PUT) /v3/appliance/{id}—When an invalid or non-existing id was used with the PATCH (or PUT) /v3/appliance/{id} endpoint, a 404 error was returned. Now, a 404 error is returned if the user doesn’t have access to the Monitoring Point specified (for example, if the Monitoring Point belongs to a different organization). A 403 error is returned if the user has access to the Monitoring Point but doesn’t have permission to update it (for example, if the user has a View Only role).
  • Deprecated API endpoint: PUT /v3/appliance/{id}—We have deprecated API endpoint PUT /v3/appliance/{id}. It will be removed in a future version of the API but existing integrations won’t be affected by the deprecation. To rename a Monitoring Point, please use PATCH /v3/appliance/{id}.
  • Deprecated support for IE 11—As of this release, APM no longer supports Internet Explorer 11. Chrome and Firefox are currently supported.
  • Classification library enhancements—The Usage Monitoring classification library has been updated with new applications, including:
    • Apple TV Plus
    • Azure Service Bus
    • BACnet
    • Bing Maps
    • Brave Browser
    • Discord
    • Disney Plus
    • Fiserv
    • HTTP AUDIO
    • IBM DB2
    • Icecast
    • iSCSI
    • Jaspersoft
    • Monster VPN
    • MS Power BI
    • MS SMServer
    • Microsoft Teams
    • MTV
    • QlikView
    • RingCentral
    • Tableau
    • Tidal
    • TikTok
    • TRACEROUTE
    • TWILIO
    • VPN Monster
    • Yahoo Web Analytics
    • Zerodha
  • Classification library improvements—Usage Monitoring application classification improvements have also been made to applications including:
    • Fuze
    • Google Hangouts