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

New Features

  • Monitor API endpoints with HTTP Monitoring!—To complement our HTML-based web application monitoring, you can now monitor API endpoints using HTTP requests. Within Experience monitoring, you now create either a “Browser workflow” (as before) or an “HTTP workflow” (new). The HTTP workflows enable you to confirm that a target can be reached, that the HTTP requests are successful, that the responses are valid, and that the response times are acceptable. Use cases include:
    • Monitor business-critical APIs either provided or consumed.
    • Assess mobile app experience by monitoring the underlying APIs on which they are built.
    • Monitor HTTP connectivity to web servers at high scale, without needing to render pages in a browser.
      Note: HTTP Monitoring requires EMP 12.5.0 Monitoring Points or later. Also, related API endpoints are currently available in BETA form under /beta/webApplication and /beta/alertProfile.
  • Improved API security with API Access Tokens—Previously, you required Basic Authentication (username and password) to access the API. Now, you can also use API Access Tokens. API Access Tokens provide better security because username and password do not need to be encoded into scripts or applications that access the API. In addition, the authentication token does not carry any user information.
    Note: The current Basic Authentication mechanism will be deprecated in the coming months. Prior to this change, you will need to migrate all scripts that use Basic Authentication to use API Access Tokens instead.

Enhancements

  • Auto-detect non-default return path public IP—Previously, if you used a non-default interface as the source for a dual-ended path, you would have to set the return path target IP address manually via the API for diagnostics to work properly. Now, this address is detected automatically, eliminating the need for the manual configuration. Note: This feature requires EMP 12.6.2 (available as of March 18, 2020) Monitoring Points or later. Also, double NATed paths only get back to the last NAT and require a manual override.
  • More efficient use of diagnostics tests—Previously, a diagnostic test was triggered each time a violation event occurred. Now, if more than five violation events occur with the same target, the same condition, and in the same direction, at the same time, diagnostics tests for only five of the violating network paths are queued to run. None of the other paths will run a diagnostic test. Instead, for each of these paths, an event is created that links to the five tests that are run. In addition, if a violation is cleared on a network path before the associated diagnostic test has had a chance to run, we remove the test from the queue and add an event that explains this.
  • Experience data now included in Application Performance Report—We have enhanced the Application Performance Report to now include Experience data. When configuring the report, you can now select Network Path only to view Delivery monitoring data, or select Network and Web Path to view both Delivery and Experience monitoring data.
  • Additional location aggregation options now available on Application Performance Report—Previously, network paths were aggregated in the Application Performance Report by the “most specific” information identified in the source Monitoring Point’s location configuration. It used the following order of preference: City, State/Province, Country, formatted text address, Monitoring Point name. You now have the ability to specify the aggregation method and aggregate by Monitoring Point, City, State/Province, Country, or Most Specific. In addition, a configuration parameter is available to limit the number of locations to display.
  • Improved web path selection in Web Dashboards—To speed up the selection of web paths when creating a Web Dashboard, we now provide the ability to check and uncheck individual web paths or all web paths in a web app group.
  • Embeddable Charts library update—A new version of the embeddable charts library is available. Update the embed code in your app/website to take advantage of the latest improvements.
  • Delete users via the API—We have added the DELETE /v3/user API endpoint to provide the ability to delete users. Note that this capability is only available to Organization Admin users.
  • Standard Enterprise App licenses displayed in groups—In order to make the Manage Licenses page perform better for customers with large numbers of Standard Enterprise App licenses, we now display groups of similar licenses rather than displaying individual licenses. Each group of licenses has values in the following fields in common: Subscription start date, Renewal period, Next renewal, and Expiration date. In addition, we now include the following actions that can be performed on a single license or on groups of licenses: Transfer Licenses, Set Description.

Resolved issues

ID Keyword Description
APM-5210 Delivery We fixed an issue where the number of hosts found using Discover Targets within Data Assessments and Discover My Network within Network Paths was different and variable.
APM-6190 Path migration We fixed an issue where, under certain conditions, path migration would fail with a generic error message.
APM-5884 Path migration We fixed an issue where, when migrating monitoring from one Monitoring Point to another, data from the primary Usage interface on the source Monitoring Point could be moved to a secondary Usage interface on the replacement Monitoring Point rather than to its primary Usage interface.
APM-5752 Experience We fixed an issue where a web path could initialize twice after it was modified.
APM-4919 Experience We fixed an issue where, when updating the “Monitor from…” part of a Web App Group, if the interface’s DHCP address had changed since it was originally configured, the system prompted that the original locations (including interfaces and IP addresses) “are no longer available” and “will be removed when you submit an update”.
APM-5785 Web Dashboard We fixed an issue where multiple Web Dashboards could use the same name.
APM-6138 Web Dashboard We fixed an issue on the Web Dashboard where, when selecting a workflow, the selection checkbox could become unchecked.
APM-6060 Usage We fixed an issue where the Usage > Monitoring Points page could be slow to load in environments with many interfaces to summarize.
APM-5367 Reports We fixed an issue where reports (for example, the Data Performance Comparison report) were slow to load.
APM-6128 Reports We fixed an issue where the Application Performance Detail Report could display network paths that were not in any of the saved lists used by the report.
APM-1180 Audit log We fixed an issue where certain Audit log messages could be truncated.
APM-5697 Notifications We fixed an issue where notifications were sent for network paths but were only enabled for web paths.
APM-6152 Embeddable Charts We fixed an issue where the Embeddable Chart script was not working on Internet Explorer 11.
APM-6056 Observer API We fixed an issue where events could stop being sent to the event integration server.

Changes to be aware of

  • Properties related to summarized data are no longer returned when raw data is requested in “path data” API endpoints—Previously, when returning data for a specific test rather than a summary of tests using the “path data” API endpoints, we would return properties that were only relevant to summarized data (period, min, and max) and set them to null. Now, these properties are only returned with summarized data. This change applies to the following API endpoints:
    • GET /v3/path/data
    • GET /v3/path/{id}/data
    • GET /v3/webPath/data
  • Diagnostic delay—For dual-ended paths, the initial diagnostic test is now delayed for a period of time to allow the target Monitoring Point to report the detected source IP address.
  • Increased time range for Web Dashboard—We have increased the maximum Web Dashboard time range from 7 days to 30 days in order to track monthly web app group and web path performance on the Web Dashboard.
  • Milestone alert profile UI change—As it is rare to set a separate alert profile on an individual workflow milestone, we have simplified Web App Group configuration by hiding this capability behind a “Set Alert Profiles for Milestones?” link.
  • Usage interface data grouped by interface activity—We have updated the Deep Packet Inspection Interfaces page (Usage > Monitoring Points) to display interfaces that have received data before those that have no activity. The benefit is that you no longer have to scroll through inactive interfaces to see the active ones.
  • Location confirmation—When editing a Monitoring Point’s location, we now provide feedback on how City, State/Province, and Country information is being interpreted and saved in order to prevent unexpected results in the Application Performance Report.
    Application Performance Report change—Previously, a web path connectivity violation was considered a violation rather than an outage on the Application Performance Report. To be consistent with network paths, it is now counted as an outage.