September 22, 2021 (vPCA 14.17.1)

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

New Products

  • Support for Cisco Catalyst—The Customer Premises Equipment 40 (cpe40) is a new Container-based Monitoring Point (CMP) that runs on the Cisco Catalyst 9300 and 9400 switches. It allows you to monitor your network from locations where you have a Catalyst 9300 or 9400 deployed without requiring additional hardware.

Enhancements

  • Export to CSV capability now available!—We now provide the ability to export list page contents to a CSV-format file, enabling you to view the page content in a spreadsheet or import it to another tool for further analysis. This functionality is available within the icon on the new Monitoring Points page, the Network Paths page, the Web Paths page, the Network Path Events page, and the Web Path Events page.
  • Connection type now available on network paths—As a tool to help diagnose issues with end-user connectivity, we now have the ability to detect whether a path from a Windows NMP is connected over a wired or wireless interface and whether or not it connects over a VPN. The connection type is displayed in a separate column on the Network Paths page and paths can be filtered, grouped, and sorted by connection type. Also, connection type information is shown in a panel on the network path details page and connection type transitions can be seen in the Events chart. Note that the connection type functionality requires Windows NMP 13.2.0 or later be deployed within your APM organization and be online. In addition, there are limitations to be aware of.
  • Wireless metrics now available on network paths—To provide greater insight when diagnosing issues on wireless networks, Windows NMP now collects several metrics that are displayed on separate charts in AppNeta Performance Manager. Metrics include Signal Quality, Link Speed, RSSI, Noise, Airtime, Retransmit, and Stations. Note that the wireless metrics functionality requires Windows NMP 13.2.1 or later be deployed within your APM organization and be online. When the time range selected is such that data is rolled up, Min/Max graphs are shown in addition to the Average graph on the Wireless chart. This helps identify spikes in metrics that might not be obvious when the data is averaged.
  • Host metrics now available on network paths—To provide greater insight when diagnosing issues on user machines, Windows NMP now collects host-based metrics in AppNeta Performance Manager. Metrics include CPU utilization, Memory utilization, and Top Processes (ordered by CPU utilization) at a point in time. Note that the host metrics functionality requires Windows NMP 13.2.2 or later be deployed within your APM organization and be online. When the time range selected is such that data is rolled up, Min/Max graphs are shown in addition to the Average graph on the Host chart. This helps identify spikes in metrics that might not be obvious when the data is averaged.
  • Specify workflow variables per source—As a complement to per-target and per-workflow variables in Experience scripts, we have added per-source variables - the ability to specify variables on a per source Monitoring Point/interface basis. The most common use case for these is where restrictions are in place to prevent simultaneous logins using the same login credentials, you now have the ability to specify different credentials for each source within a web app group.
  • Multi-Factor Authentication (MFA) now supported in Experience scripts—Selenium scripts within Experience monitoring now support MFA using Time-based One Time Passwords (TOTP). This feature enables Experience monitoring to be used in enhanced security environments that require MFA.
  • WCAG 2.1 Improvements—We have made a number of accessibility enhancements for WCAG 2.1 compliance. Enhancements were made to message banners, the login page, and all icons.

Changes to be aware of

  • Legacy Monitoring Points going offline—To harden security, we have deprecated TLS1.0/1.1 in favor of TLS1.2. In this release all TLS1.0 and TLS1.1 connections are blocked. As a result, legacy Monitoring Points will not be able to connect. 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.
  • Increased password complexity requirement—We have increased the password complexity requirement for Monitoring Point access. Valid passwords now require the following:
    • A minimum of 8 characters
    • At least one of each of the following:
      • A lower case character (a through z)
      • An upper case character (A through Z)
      • A number (0 through 9)
      • A special character (!“#$%&‘()*+,-./:;<=>?@[]^_`{|}~)
  • Transition to new Monitoring Points page complete—We have now fully transitioned to the new Monitoring Points page and have removed the previous page.
  • UI changes on network path performance charts—We have updated how data is displayed when interacting with data points on the network path performance charts as follows:
    • No interaction - Data for the most recent data point is displayed in the lower left of the chart.
    • Hover over a data point - Associated data is displayed in the lower left of the chart.
    • Click a data point - Associated data is displayed in a box in the upper right of the chart.
  • Updated headers on Network Timeline page—To make commonly used functionality easier to access, we have changed the name and updated the functionality accessed from the header of the path performance page in Delivery monitoring. The page is now called “Network Timeline” and includes path source and target, a link to modify the path configuration, a selector for sharing a link to the page or downloading a PDF, as well as a link to disable monitoring on the path.
  • Updated headers on Web Timeline and Web Drill-down pages—To uniquely identify a web path and to make commonly used functionality easier to access, we have changed the name and updated the information shown on the header of both the Test Timeline and Test Drill-down pages in Experience monitoring. The Test Timeline page is now called “Web Timeline”. The Test Drill-down page is now called “Web Drill-down”. In addition to the name changes, the headers now include path source and target, a link to modify the web app group, a link to modify the workflow, a selector for sharing a link to the page or downloading a PDF (Web Timeline page), and link for scheduling a report (Web Timeline page).
  • Web path custom tags in alert notifications—Custom tags associated with a violating web path are now included in email notifications and in Web Application Event objects sent via Event Integration.
  • Shared dashboards reflect current settings—We have updated dashboard sharing so that the shared dashboard reflects the currently configured time period rather than the current time.

Resolved issues

ID Keyword Description
APM-11041 Connectivity We fixed an issue where a Monitoring Point could disconnect then reconnect several times in an hour.
APM-10002 Monitoring Points We fixed an issue where the format of the “Last Changed” time in the Monitoring Point details pane on the Monitoring Points page was MM/DD/YYYY instead of YYYY/MM/DD.
APM-10531 Delivery We fixed an issue where creating multiple network paths to multiple Monitoring Points at once using the path creation tool could fail.
APM-9728 Delivery alerts We fixed an issue where, for network paths with a custom time range set for alerts, hovering over the network path status icon on the Network Paths page showed an inaccurate status (“None Active”) for “Alert Profile” and “Time Range”.
APM-10176 Path Template Group We fixed an issue where adding an interface using the POST /v3/pathTemplateGroup/{id}/monitoringPoint API endpoint added the interface specified but did not remove it from the list of available sources in the Path Template Group.
APM-10115 Routing diagrams We fixed an issue where shared IPv4 address space on AWS resulted in confusing routing diagrams.
APM-10227 Tags We fixed an issue where Tags configured on certain network paths were not being honored or retained.
APM-10331 Diagnostics We fixed a Diagnostic message that indicated a target Monitoring Point was not in the same organization as the source when actually the target was offline.
APM-9994 Event Integration We fixed an issue where duplicate Connection Lost Sequencer Events were transmitted in Event Integration (observer) output.
APM-10365 API We have updated the “limit” documentation for /v3/path/data within the Admin API to indicate that the default maximum number of results to return is 100 rather than 1000.
APM-10827 Experience We fixed an issue where Experience Load could show 0% even with a large number of web paths.
APM-10026 Experience We fixed an issue where, when editing an Experience workflow, trying to select text in a field by clicking and dragging the cursor over it caused the entire row to be moved instead.
APM-10649 Usage We fixed an issue where a Capture Interface name could not be set or changed on the Manage Monitoring Points page.
APM-10043 Dashboards We fixed an issue where selecting one dashboard could select two instead.
APM-10405 Dashboards We fixed an issue where the TreeMap on the Overview page could fail to load.
APM-10782 Upgrades We fixed an issue where the “Upgrade Required” number listed on Dashboards > Overview was incorrect.
APM-7104 Reports We fixed an issue where the Application Performance Report (now the Application Quality Report) could report that network paths from offline Monitoring Points were “OK”.