July 3, 2019 (vPCA 12.11.1)

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

New products and features

  • Multi-path Route visual now available!! - Fully integrated with Delivery monitoring, the multi-path Route visual is now available. This feature provides a way to visualize routing for up to 20 network paths over time, enabling you to investigate problems that may be due to routing. The Route visual instantly shows hops that are common to multiple paths and how this routing changes over time.



  • Preview via Web Proxy—We have updated the Preview feature in Experience monitoring to use the proxy settings configured on the web app group being tested. To make them easier to select, the Monitoring Points for that web app group are grouped at the top of the dropdown, under “Configured Monitoring Points”.
  • Compare DNS server performance on different web paths—We have added the ability to compare DNS performance across web paths as a way to understand how DNS may be affecting web path performance. This information is available in the new DNS tab when you compare web paths.
  • Customizable columns on Web Paths page—The Web Paths page has been enhanced to include customizable columns like the Network Paths page.
  • HTTP Authentication to a target—Previously, HTTP Authentication could be defined on a per workflow basis within a web app group configuration. Now, it can also be specified on a per target basis. If there is an overlap between the two configurations, the workflow configuration takes precedence.
  • PAC file support added—We now support the use of Proxy Auto-Config (PAC) files for proxy configuration. All network paths and web paths from a Monitoring Point that uses a PAC file follow its proxy definitions. This feature can be configured in the APM UI when creating or editing a web app group. It can also be configured using the /v3/webApplication APM API endpoint. The feature requires EMP 12.2.0 or later software on your Monitoring Points.
  • Easier to access web proxy settings—We have moved the web proxy settings within the web app group configuration so that you no longer have to drill down through an Edit menu. You can now access the Edit Proxy Settings dialog when you configure the source Monitoring Point during web app group creation or edit.
  • “Proxy Type” filter added—We have added the ability to filter by “Proxy Type” to the Web Paths page. In addition, the “Proxy Type” column is also available on the page and web paths can be sorted by this column.
  • Configurable web path timeout period—You can now reduce the web path timeout period so that if a timeout does occur the delay before running subsequent scripts is reduced. The timeout can be configured during web app group creation or edit. It can also be configured in the APM API using the WebPathConfig object in the /v3/webApplication endpoint. The minimum timeout period is 25 seconds.
  • Resolved IP address in Test drill-down—We have updated the Test Drill-down page to include the resolved IP address for each milestone. This is useful when trying to determine if a specific server is impacting performance.


  • New applications supported—The Usage Monitoring classification library has been updated with new applications including:
    • HBO Nordic
    • Elisa Viihde
    • Yle Areena
    • Viaplay
    • MTV3
  • Application improvements—Application classification improvements have also been made to applications including:
    • UDP


  • Control Usage monitoring from the API—We have enhanced the APM API so that you can now start and stop Usage monitoring on an interface. In addition, you can now check Usage monitoring status. /v3/flow/appliance/{id}/interface/{intf}/action/{action} is used to start and stop Usage monitoring on an interface. /v3/flow/appliance/{id}/interfaces/state is used to check the state of Usage monitoring.
  • View all event integrations—You are now able to use the GET /observer/ endpoint to view all event integrations, not just those created by your user ID. This capability is only available to users with the “Organization Admin” role using the allUsers=true parameter. You will see the event integration information for users you have access to.

Resolved issues

ID Keyword Description
APM-2045 Delivery We fixed an issue where a network path could become unlicensed.
APM-1609 Network Paths We fixed an issue where the column header configuration on the Network Paths page was lost when navigating between Organizations.
APM-2805 Path template groups We fixed an issue where the Path Template Groups feature was not updating all changed path properties as expected.
APM-2604 Usage We fixed an issue where the r90 Monitoring Point was not allocating enough resources to process Usage monitoring files. This resulted in poor performance when viewing the Usage data.
APM-2373 Usage We fixed an issue where the Usage Traffic Summary page could wait indefinitely.
APM-3081 Usage charts We fixed an issue where Usage data was not being rolled up properly for r90 and r1000 Monitoring Points. The symptom was that Usage chart data could look different depending on when you accessed the charts.
APM-2689 Packet capture We fixed an issue where packet capture passphrases that contained special characters rendered the captures irretrievable.
APM-897 Administration We fixed an issue where, in some cases, an Organization name could not be changed.
APM-3047 Monitoring Point setup We fixed an issue where the configuration file generated by the Add Monitoring Points wizard (USB configuration method for physical Monitoring Points) contained a NULL value for the password.
APM-2732 Event Integration We fixed an issue where the observer API could fail to send POST messages via HTTPS.
APM-2721 Reports We fixed an issue where the Experience Detail Report was being sent for the wrong web path.
APM-1448 Reports We fixed an issue where the Service Quality Report was sometimes missing data in the Violation Breakdown chart due to daylight savings time.
APM-686 Reports We fixed an issue where the link at the top of the Experience Detail report (emailed or scheduled version of the report) pointed to the Network Paths page rather than the Experience Test Timeline page.
APM-2733 API We fixed an issue where, when page and limit parameters were specified for the /v3/path/data and /v3/webpath/data endpoints, the same path could be reported across multiple pages and pages with fewer results than the specified limit could be returned.
APM-2954 API We fixed an issue where clear events were not being sent by the observer API.
APM-3375 API We fixed an issue where the APM API endpoint PATCH /v3/webApplication/{id} could incorrectly return an error message regarding multiple locations with the same Monitoring Point name and interface.

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