September 18, 2018 (vPCA 11.16.1)

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


  • The new Network Paths page is live!—The changes we have been making to the Network Paths page since release 11.12.0 are now live with more to come. In addition to the changes you could preview in previous releases, we have added the following:
  • Interactive status summary bar—We have also added an interactive status summary bar to both the Web Paths page and the new Network Paths page. Clicking a status adds it to the search filter.
  • Dedicated maintenance port—We have added the ability to dedicate a second Ethernet port for APM-Private maintenance access. This feature is for those customers that require maintenance access via a separate network. At this time, this feature can only be configured by contacting AppNeta Support.
  • Single Sign-On external SP support—We have added the ability for APM-Private Cloud to access an external SAML Single Sign-On (SSO) service provider (SP). In previous releases, only an on-premise SP could be accessed.
  • Support for a second SNMP notification sender—We have added the ability to specify a second SNMP notification sender to provide SNMP redundancy, to specify multiple NMS hosts, and to send informs in addition to traps. When a second notification sender is specified, both the primary and secondary will send all traps or informs to the specified NMS(s).
  • Higher password strength requirement—We have increased the password strength threshold to provide better system security. Specifically, all passwords must contain a minimum of eight characters and must include - uppercase alphabetic, numeric, and special characters.
  • “clickIfVisible” Selenium command added to Experience—We have added support for the “clickIfVisible” Selenium command to the Experience monitoring functionality. It is an AppNeta-developed command that will click an element only if it is present and visible. This command requires APM-Private Cloud version 11.16.1 or later and EMP version 11.0.0 or later.
  • Automation assistance—We have made a number of additional API enhancements to make it easier to automate network path, web path, and organization changes. These enhancements include:

    • the ability to retrieve alert time ranges
      • GET/v3/timeRange
    • the ability to bulk delete network paths
      • DELETE /v3/path
    • the ability to make bulk changes to the groups that network paths belong to
      • PATCH /v3/path
    • the ability to retrieve/add/update Experience script variables for both targets and workflows in applicable /v3/webApplication endpoints.
    • the ability to create and retrieve QoS templates via the API. An Organization Admin role is required to use the POST endpoint. To apply a QoS template to one or more network paths, use the PATCH /v3/path endpoint.
      • POST /v3/qosTemplate
      • GET /v3/qosTemplate
    • updates to /v3/organization endpoints to return an organization’s siteKey in their responses
      • GET /v3/organization
      • POST /v3/organization
      • PUT /v3/organization/{id}

For more information on these 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-163 Delivery We have updated the Data Loss and Voice Loss charts to include the number of packets sent and lost in addition to the % lost.
CS-10122 Delivery We fixed an issue where a user with View-only privileges was able to initiate a Diagnostic test.
AV-2534 Experience We fixed an issue where the Response Time chart displayed incorrect values.
AV-3800 Experience We fixed an issue where Apdex thresholds set on a per milestone basis were not being used as expected.
APM-443 Experience We fixed an issue where the color of the path location dot on the Experience GeoMap did not accurately reflect the Apdex score.
FV-1700 Usage We fixed an issue where, in Usage monitoring, Custom Applications were not being applied to Monitoring Points.
APM-413 NTP We fixed an issue where Monitoring Point status shows an NTP error but it is actually synchronized properly with its configured NTP servers.

Deprecated Features

  • SNMP NMS—We have deprecated the SNMP NMS feature as it was not being used by customers and it resulted in unnecessary traffic being sent between APM and each Monitoring Point.
    Note: This change does not affect the SNMP notifications feature.

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