January 27, 2021 (vPCA 13.24.1)

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

New Features

  • Custom Tags are now available!!—Custom Tags are a powerful and flexible way to group network and web paths based on categories that you define and that make sense to your business. They enable you to filter, group, sort, and take actions on the set of paths you are interested in - especially important when trying to manage networks with hundreds of sites and thousands of network paths. For example, if you are interested in the service levels achieved by each of your ISPs, you could tag paths with the ISP responsible for them. If your support teams are each responsible for a subset of your overall infrastructure, you could tag paths by the support team responsible for them. This allows each team to see just the paths relevant to them. The possibilities are endless. Whatever makes sense to your business.
  • Create and assign tags—You can create and assign tags when a network path is created - either individually or as part of a Path Template. Tags can also be created and assigned within the Network Paths and Web Paths pages.
  • Tags in alerts—Tag information associated with affected paths will also be included in email notifications and as part of the data returned by Event Integration for Service Quality Events and Network Change Events.
  • API support for tags—There are also a number of tag-related API endpoints available:
    • GET /v3/tag - retrieve tags
    • POST /v3/tag/assign - assign a tag
    • POST /v3/tag/remove - remove a tag
    • POST /v3/tag/removeAll - remove all tags from a list of resources
    • GET /v3/tag/{id} - retrieve a tag by its ID
    • GET /v3/tag/{id}/resource - retrieve all resources a tag is assigned to


  • New Quick Tags enhance path filtering—The Search/Filter bar on the Network Paths and Web Paths pages now include Quick Tags to help specify tag filters faster. As a search/filter keyword is typed in the Search/Filter bar, all Custom Tags that match the keyword are displayed in a “Quick Tags” section below the Search/Filter bar. Selecting a Quick Tag completes the keyword specification.
  • Filter and group by Monitoring Point Type—As part of the effort to provide more flexible network path filtering and grouping options, we have added a Monitoring Point Type filter and group on the Network Paths page. A Monitoring Point Type column is also available within the Columns selector on that page.
  • Easier to associate milestone names with Web Path data—We have updated the GET /v3/webPath/data API endpoint to include the Web App Group ID (webAppId). This ID can be used with GET /v3/webApplication/{id} to associate milestone names with the data returned by GET /v3/webPath/data.
  • Selected organization persisted across logins—For users with access to multiple child organizations as defined within your AppNeta Performance Manager account, we have added a small convenience for you. Rather than having to select an organization each time you log in, now, once it is selected, the organization persists until you change it. In most cases, this will save a step each time you log in.

Resolved issues

ID Keyword Description
APM-6425 Delivery We fixed an issue where the “SourceIP” variable, used when creating a network path name, was providing the IP address of the Default interface rather than the IP address of the source interface.
APM-5189 Delivery We fixed an issue where, when grouping by Path Template Group on the Network Paths page, only network paths that were created by a Path Template Group were displayed.
APM-7828 Delivery We fixed an issue where the location property associated with a network path was not updated when the target location was modified.
APM-7338 PathTest We fixed an issue where, when switching between Data and Voice within PathTest, the Source and Target information could change in some cases.
APM-7676 Path Plus Tools We fixed an issue with Path Plus Tools where PathTest results could be displayed under all tabs (PathTest, NSLookup, TraceRoute, and Ping).
APM-6996 Diagnostics We fixed an issue where the hop diagram at the top of the Diagnostics page could render incorrectly.
APM-8170 Saved Lists We fixed an issue where, if a Monitoring Point was removed from a Saved List, the list of associated paths would be emptied.
APM-8337 Route Visualization We fixed an issue with Route Visualization where two Monitoring Points with the same source IP would show as a single source.
APM-5705 Alerts We have updated the workflow on the Edit Alert Profile page for both Delivery alerts and Experience alerts to make it clear that, after making a change to a condition on a custom alert profile, you must click the Replace button before clicking the Update button.
APM-7736 Experience We fixed an issue where transaction time results were being displayed for time periods prior to release of the feature in August. Under certain conditions, such pre-release results could be incorrect. Now, transaction time results commence as of release of the feature.
APM-7708 Experience We fixed an issue where Network and Server times on the Transaction Time chart could be lower than those appearing on the Page Load chart.
APM-7703 Experience We fixed an issue where the DNS Resolution Time chart was not rendering properly when comparing more than 10 web paths.
APM-7803 Experience We fixed an issue where the Apdex score in the Latest Transaction Details section of the Test Timeline page could be incorrect.
APM-8188 Experience We fixed an issue where the Experience script preview functionality was not working properly on updated Global Monitoring Points.
APM-7694 Apdex We fixed an issue where an Apdex alert could be triggered even though the Apdex score was within configured thresholds.
APM-7733 Usage We fixed an issue where, after migrating Monitoring Points, there were cases where historical Usage data was not available as expected.
APM-7930 Usage We fixed an issue where, after a Monitoring Point migration, previously created Saved Views were not accessible.
APM-8008 Usage We fixed an issue where a Saved View in Usage was not being migrated to a new Monitoring Point with all the other monitoring data.
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.
APM-7867 Reports We fixed an issue where the Service Quality - Top Offenders Report could display the message “No service quality violations for the network paths and time period specified.” even though there were violations to report.
APM-8449 Reports We fixed an issue with the Top Offenders Report where only the top five offenders were being shown.
APM-8012 Upgrade We fixed an issue where Monitoring Points were upgraded automatically even though they were set for manual upgrade.
APM-8430 CMP installation We fixed an issue where certain SSO users received “Access Denied” messages when downloading the Container-based Monitoring Point image.
APM-7562 Monitoring Point We fixed an issue where it could take several minutes to add a Monitoring Point.
APM-7975 API We fixed an issue where certain API calls were incorrectly returning a 400 (Bad Request) response.

Changes to be aware of

  • Deprecated TLS1.0 and TLS1.1 support—As part of our ongoing commitment to security, this release of AppNeta’s Private Cloud service will support the ability to block all TLS1.0 and TLS1.1 connections. We’re making this change to ensure security of data in transit.
    What does this mean? As part of your upgrade, AppNeta will work with you to define a cutover date when TLS1.0/1.1 will be blocked.
    What’s next? Prior to the cutover date, you will need to:
    • Migrate all Legacy Monitoring Points (m20, m22, m30, r40, r400 and the Software Sequencer) to current generation Monitoring Points as the older Monitoring Points only support TLS1.0/1.1.
    • Update all non-compliant API requests to use TLS1.2 over HTTPS.
    • Most major browsers no longer support TLS1.0 and TLS1.1 so no action is required provided you are using a recent browser version: Google Chrome, Microsoft Internet Explorer and Edge, or Mozilla Firefox.

    Please contact your AppNeta Customer Success representative if you have any questions or for help with a transition plan.

  • NMP 8.4.x and lower and all CMPs support only “External” upgrade mode—External upgrade mode (Upgrade Type column on the Monitoring Points page = “External”) means that a Monitoring Point cannot be upgraded from the Monitoring Points page. For these, “Upgrade Settings” and “Upgrade Now” actions (bulk and per Monitoring Point) are not available.
  • macOS NMP 12.x and later support only “Auto” upgrade mode—Monitoring Points that use the “Auto” upgrade mode check for upgrades periodically and upgrade themselves when new versions are available. Their upgrade mode and timing cannot be changed from APM.
  • Beta versions of endpoints removed—/beta/webApplication and /beta/alertProfile endpoints have now been removed as all changes to them have been available in the /v3 versions of these endpoints since June 2020.
  • Extended Experience script timeout—The maximum Experience script timeout has been extended from 60 seconds to testing interval / 3. This can be set via the APM UI when creating or editing a Web App Group or via the APM API (using /v3/webApplication/{id}). NOTE: Avoid setting an overly long timeout period. If the script does time out, it will consume resources on the Monitoring Point for the full duration of the timeout period.
  • Transition from Linux software sequencers—Linux software sequencers can no longer be created via the Add Monitoring Points workflow. Container-based Monitoring Points should be deployed instead.
  • Security improvements—We’ve made a number of security related improvements updates to further harden the product.