March 29, 2019 (vPCA 12.4.1)

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

New products and features

  • r1000 Monitoring Point!—–Application updates are included in preparation for the new data center Monitoring Point, r1000.
  • DNS monitoring now available! - Available now for Selenium-based web paths on EMPs; nothing to configure and no additional licensing required. DNS monitoring provides insight into the effect of DNS resolution times on end-user Experience. The DNS chart shows average and maximum DNS resolution times as well DNS service availability for up to a year. In addition:
    • Requires EMP 11.3.0 or later - DNS monitoring data can be collected from Enterprise Monitoring Points (EMPs) running software version 11.3.0 or later.
    • DNS server settings in Web Path shared links - The share link on the Test Timeline page provides all DNS server settings to the link recipient.
    • DNS server performance comparison - The DNS chart shows data for one or more DNS servers in addition to the fastest responses across all servers. This enables you to compare the performance of the DNS servers you use and to identify when a particular server is having problems.
    • Retrieve DNS data in bulk - We have added an API endpoint (GET /v3/dns/webPath/data/) that allows you to retrieve DNS data in bulk. It works the same way that GET /v3/path/data works for retrieving network path data.
  • AppNeta Education Portal! - AppNeta now provides online training through the AppNeta Education Portal. Visit the portal for complimentary best practices, tips, and tutorials. Request an invitation for your users by emailing


  • SNMP traps for Monitoring Point connectivity—We have added SNMP traps to indicate Monitoring Point connectivity status. The three new statuses messages include: Monitoring Point created, Monitoring Point available, and Monitoring Point cannot be reached.
  • Changes to report launching—We have changed the behavior of the Service Quality and Performance Overview reports so that they do not automatically run on page load. Instead, they must now be run either by scheduling them or by pressing a Run Report button.
  • Updated messaging—We have updated the messaging a Standard or View Only user sees when they try to login and no Monitoring Points are defined for their organization. Previously, they received a cryptic “Insufficient Privileges” message. Now, the message explains that their administrator must first set up at least one Monitoring Point before they can proceed.
  • Updated password reset workflow—In order to tighten security around user passwords, we have changed the password reset workflow. Rather than the Organization Administrator changing a user’s password directly, they now generate an email for the user to reset their own password.
  • License names have changed—With the introduction of new Monitoring Points (m50, m70, and r90), license names have changed. The new base license names are found on the Monitoring Point Licensing page.


  • Delivery monitoring using custom ports - We have updated Delivery monitoring to allow the use of custom source/destination UDP and TCP port numbers for Continuous Path Monitoring (CPA). Previously, default port numbers were used.
  • “Importance” and “Type” filters added—We have added the ability to filter by “Importance” and “Type” to the Network Paths page. In addition, “Importance” and “Type” columns are also available on the page.
  • “Active Alert Profile” filter added—We have added the ability to filter and group by “Active Alert Profile” to the Network Paths page. In addition, the “Active Alert Profile” column is also available on the page and network paths can be sorted by this column.
  • Time range selector now remains visible—We have updated the Network Path Performance page and the Web Path Test Timeline page so that the time range selector remains visible as you scroll down through the charts. Previously, it would scroll off the page.
  • PathTest access control added—We have added the ability to specify which users are able to run PathTest with the new “PathTest” add-on privilege. In previous releases, all user roles except View Only were able to run PathTest. Now, by default, only Organization Admin and Advanced users can run PathTest but any user can have PathTest ability enabled or disabled by an Organization Admin.


  • Web path and network path state now linked—Previously, a web path’s enable state was independent of the underlying network path state. Now (subject to some conditions), if web path monitoring is disabled or enabled, the related network path will also be disabled or enabled.
  • Modified Experience—We have changed the ordering of the Experience menu in order to promote the use of the Web Paths page as the “home base” for Experience monitoring. The Web Paths page enables you to see the status of your web paths, to rapidly filter down to paths of interest, to compare paths, and to easily edit a related web app group configuration.
  • Edit a Web App Group from the Web Paths page—We have added the ability to edit a Web App Group from the Web Paths page. This eliminates the need to go back to the Web App Groups page and find the appropriate Web App Group to edit.
  • Test results displayed in separate tabs—In order to assist with comparing Experience test result details, clicking a data point on some Experience charts (End User Experience, Milestone Breakdown, and Apdex Score) now opens a Test Drill-down page in a separate tab. Previously, the page was opened in the same tab, replacing the Test Timeline page.
  • Experience Chrome changes—We have updated the Test Timeline page within Experience to indicate when the version of Google Chrome used by a Monitoring Point is changed. This is useful information when trying to determine why a script executes significantly faster or slower or behaves differently than prior to the change. The Google Chrome version was changed in EMP 11.4.1.
  • HTTP Authentication available in Preview—We have updated the Preview feature you see when adding or editing an Experience workflow so that HTTP Auth parameters can be used to authenticate the target URL.
  • Additional HTTP authentication schemes available in Selenium—We have added support for additional HTTP authentication schemes when using Selenium scripts. Credentials are added via the APM UI when creating a script or via the APM API (authUsername and authPassword within /v3/webApplication endpoints). These credentials are used by the Selenium open command if the target server challenges for authentication. If not challenged, the open command performs exactly as it did previously. Basic, Digest, NTLM and Negotiated authentication schemes are now supported. The openAuthenticated command can also be used for Basic authentication, as before.


  • Enable Organizations for SSO via the API—We have created new API endpoints that enable organizations to be associated with an Identity Provider. This is useful, for example, when creating a child organization and being able to associate it with the Identity Provider used by its parent. New endpoints include:
    • GET /identityProvider endpoint
    • PATCH /identityProvider/{id}/organizations
  • Configure a web path proxy from the API—We have added the ability to configure proxy settings for web paths from the APM API. The following endpoints can be used:
    • POST /v3/webApplication
    • PATCH /v3/webApplication/{id}
    • PUT /v3/webApplication/{id}
  • Modify monitoring interface from the API—We have added the ability to change an interface being used by a web path without losing historical data, orphaning network paths, or requiring additional licenses. This API change allows you to continue monitoring when interfaces need to change subnet masks or names. The following endpoints have been added: 
    • POST /v3/appliance/{id}/interface/moveAll - moves monitoring to a new interface
    • GET /v3/appliance/{id}/interface - lists interfaces available on a Monitoring Point
  • Web application alerts via API - We have added the ability to monitor web application events via the /v3/observer API endpoint. This is in addition to the test events, sequencer events, and service quality events that can currently be monitored. See APM Event Integration for details. In addition to this enhancement, we’ve made changes to the POST /v3/observer API endpoint to improve event delivery performance.
  • Retrieve web path data in bulk—We have added an API endpoint (GET /v3/webPath/data/) that allows you to retrieve web path data in bulk, rather than one web path at a time. It works the same way that GET /v3/path/data/ works for retrieving network path data.
  • For more information on the API enhancements and on all of the other capabilities available through the APM API, see the AppNeta Performance Manager documentation.

Resolved issues

ID Keyword Description
APM-833, APM-917 Delivery We fixed an issue where sorting based on columns containing metrics on the Network Paths page was not working properly.
APM-671 Delivery We fixed an issue where sorting based on the Target Type and Path Template Group columns on the Network Paths page was not working properly.
APM-713 Delivery We fixed an issue where the link to the AppNeta MIB from the Manage SNMP page was broken.
APM-773 Delivery We fixed an issue where, after setting the Monitoring Point Interface on a network path to something other than “Auto”, when you go back to re-edit the path configuration, the Monitoring Point Interface displays “Auto”.
APM-659 Delivery We fixed an issue where a network path that was created automatically as part of a web path and then renamed, could not be deleted.
APM-921 Delivery We fixed an issue where changes made using the Manage Groups page were not reflected on the Network Paths page.
APM-1178 Delivery We fixed an issue where, on dual-ended paths, the percentage-based Inbound Capacity threshold was getting set based on Outbound capacity measurements.
APM-840 Delivery We fixed an issue where network paths were not showing a link in the “Last Diagnostic” column on the Network Paths page when they should have been.
APM-1692 Delivery We fixed an issue where the Network Paths page show only a partial list of network paths.
APM-710 Diagnostics We fixed an issue where Diagnostics test results could show the wrong hostname at the final hop.
APM-2301 Voice/Data Assessments We fixed an issue where network paths sourced from, or targeting, virtual Monitoring Points did not show up on the path list when running a voice or data assessment.
APM-995 Experience We fixed an issue where the Web App Group name was not appearing in the header of some pages when modifying a single Web App Group.
APM-297 Experience We fixed an issue where Experience script milestones could report success even when the script failed to complete.
APM-73 Experience Previously, when creating a script in the Experience module, the preview feature would display blank pages to represent screenshots attempted before the target page was renderable. To clarify this “non-renderable” state, we have replaced the blank pages with pages that say “Test is underway …”.
APM-1246 Experience We fixed an issue where the Apdex score was being evaluated and events were being generated during periods when the Experience workflow was not completing successfully.
APM-1502 Experience We fixed an issue in the Experience Web Dashboard where an AppNeta script symbol could be associated with an unlicensed Selenium path. The Selenium script symbol is now associated with both licensed and unlicensed Selenium paths.
APM-2023 Experience We fixed an issue where the HTTP Throughput and Response Time tables could be empty even though the associated charts showed data.
APM-1964 Experience We fixed an issue where trial “Chrome Early Access” GMPs were still available as an option on the Request Global Monitoring Point screen.
APM-241 Experience We fixed an issue where the preferred web dashboard on the Web Dashboard page was not being saved when a new dashboard was selected.
APM-2249 Experience We updated the Comparison Views page in Experience so that, by default, Comparison Views are sorted alphabetically by Name.
APM-2235 Experience We fixed an issue where the resource list that appears beneath the “JavaScript Errors” section on the Test Drill-down page could appear with no data (blank). The workaround was to click one of the column headers. The workaround is no longer necessary.
APM-2049 Experience We fixed an issue where the Web Alert Profiles popup could show the same condition multiple times within the same profile. Related to this, we fixed an issue where some web path alerts were not being triggered when they should have been.
APM-689 Usage We fixed an issue where an error message (“Error retrieving flow data”) could be displayed when viewing the Usage Summary page.
APM-1142 Usage We fixed an issue where sorting columns on the Application Usage Saved Views page caused an error when the page was rendered.
APM-1176 Usage We fixed an issue where, when using Saved Views, Usage data was slow to load.
APM-2373 Usage We fixed an issue where the Usage Traffic Summary page could wait indefinitely.
APM-434 Notifications We fixed an issue where Web Path Events in the Event Digest email were not being sorted properly.
APM-1247 Notifications We fixed an issue where violation or clear event notifications could get lost.
APM-652 Reports We fixed an issue where the “Saved List” field in the Application Performance Detail report was not saving the specified smart list.
APM-865 Reports We fixed an issue that stopped some scheduled reports from being sent as expected.
APM-1664 Reports We fixed an issue where emailed performance reports and service bulletin notifications were enabled by default for users created via single sign-on (SSO). They are now disabled by default.
APM-2006 Reports We fixed an issue where, once scheduled, the Application Performance Summary Report could not be edited as the Save button was disabled.
APM-1617 Reports We fixed an issue where, when running saved report filters with filtered paths set, the filtered paths would be ignored.
APM-1376 SNMP We fixed an issue in the user interface where a non-blank “Engine ID” value was required for v2c SNMP traps. This field is now removed for v2c but is still required for v3.
APM-1335 SNMP We fixed an issue where SNMP traps were not sent when there were multiple trap senders configured and one was offline.
APM-1635 SNMP We fixed an issue where SNMP v2c Traps were sent as SNMP v2c Informs.
APM-1540 SNMP We fixed an issue where clear traps were not being sent when a script error was cleared.
APM-2206 SNMP We fixed an issue where SNMP events were not being sent in all cases.
APM-2050 SNMP We fixed an issue where the network group name, rather than the web app group name, was being sent in “web app name” field in the SNMP trap details.
APM-945 Setup We fixed an issue where the APM relay server referenced in the USB and Direct connect configuration files was incorrect. It was instead of
APM-1674 UI We fixed an issue where the APM user interface became unresponsive.
APM-2268 UI We fixed an issue that caused the APM UI to return an error when an unusually large number of network events were being received.
APM-2091 UI We fixed an issue where the user interface could be very slow to respond. In particular, this behavior was noticed when opening network paths.
APM-1572 Connectivity We fixed an issue that could cause Monitoring Points to go offline for 5 minutes and then reconnect. During the time offline, events were raised and alert emails were sent.
APM-950 Licensing We fixed an issue where a Standard Application License could not be assigned to m70 or r90 Monitoring Points.
APM-903 Licensing We fixed an issue where web paths and network paths would appear as unlicensed even when licenses were available.
APM-2010 Licensing We fixed an issue where, when a web application associated with a Global Monitoring Point (GMP) in a web path was updated, network paths on w20/w30 Monitoring Points in the same region as the GMP became unlicensed.
APM-2119 Location We fixed an issue where “Set Location” was presented as part of the license assignment screen.
APM-1070 Helpdesk We have updated the AppNeta helpdesk single sign-on page to allow connections via port 443 (standard HTTPS port). It was using port 9031 previously.
APM-1641 s35 We fixed an issue where the connection between an s35 (software sequencer) and APM could close during diagnostic testing and cause the diagnostic to fail.
APM-1856 APM server We fixed an issue that caused extremely high CPU utilization on a number of APM servers.

Changes to be aware of

  • Change to Support portal—AppNeta Support is moving to a new ticketing system for better customer data integration and reporting. You will notice that if you access the Support portal directly you will be redirected to a login page to authenticate. If you are already authenticated within APM you will not need to reauthenticate.

Known issues

  • Duplicate data returned - When the limit parameter is used with bulk data endpoints GET /v3/path/data/ and GET /v3/webPath/data/ and the response has multiple pages, data for some paths may be duplicated in separate pages. To work around this issue, only use data for the first occurrence of a given path.

There are also changes to Monitoring Points related to this release. These are documented in the following Monitoring Point release notes: