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

Enhancements

  • Path Template Groups now include interface support—Path template groups help you manage your path configurations when the same target is being monitored from multiple monitoring points. In this release, we have added the ability to specify one or more source monitoring point interfaces as network path sources and have simplified the workflow on the Path Template Groups page. The Path Template Groups page now displays both Path Templates and source interfaces making it easier to see the group’s complete scope. In addition, you can add, delete, or modify Path Templates and source interfaces from this page. Once updated, the changes are automatically propagated to all source monitoring points.
  • “Path Template Group” filter added—We have added the ability to filter and group by “Path Template Group” to the Network Paths page. In addition, the “Path Template Group” column is also available on the page and network paths can be sorted by this column.
  • Convenient access to create Path Template Group page—We have replaced the “+ Network Path” button on the Delivery > Network Paths page and the Dashboards > Overview page with a dropdown that provides options to create a Network Path or a Path Template Group.
  • Copy results from Path Plus tools to the clipboard—To make it easier to share results from Path Plus tools like PathTest, NSLookup, TraceRoute, and Ping, we have added a Copy to Clipboard button to each of the tools.
  • Change Experience scripting language—Previously, once you had selected the scripting language on a web path it could not be changed. Now, you are able to change the scripting language without losing path history.
  • Default alert profile assigned to new web paths—In order to provide more valuable monitoring on web paths, we now assign a default alert profile to all newly created web paths. The alert profile, called “Browser Web Path Default” (formerly called “Script Completion”), catches basic monitoring issues that you should be aware of: Connectivity issues, HTTP Errors, and Script Errors. This alert profile assignment can be changed or removed if required, but it ensures that there is some alerting by default. See the Experience Alerts page for information on creating and applying web path alert profiles.
  • Create alert profiles via the API—We’ve added the ability to create and manipulate both network and web path alert profiles via the alertProfile group of endpoints in the APM API. Previously, this could only be done using the Web interface. New functionality includes: GET /v3/alertProfile, POST /v3/alertProfile, DELETE /v3/alertProfile/{id}, GET /v3/alertProfile/{id}, and PUT /v3/alertProfile/{id}.
    In addition, you can now obtain and apply alert profiles on a workflow within a web app group using the new alertProfiles object within the existing userFlows object in /v3/webApplication. You can also obtain and apply alert profiles on a specific web path (overriding the alert profile set for its workflow) using the new alertProfiles object within the existing webPathConfigs object in /v3/webApplication.
  • Access voice and video test results via the API—You can now access voice and video test results using new API endpoints. The endpoints include:
    • GET /v3/voiceTest - retrieve voice test meta-data (information about the tests)
    • GET /v3/voiceTest/data - retrieve voice test data
    • DELETE /v3/voiceTest/{id} - delete a voice test
    • GET /v3/videoTest - retrieve video test meta-data (information about the tests)
    • GET /v3/videoTest/data - retrieve video test data
    • DELETE /v3/videoTest/{id} - delete a video test
  • New capabilities on the Application Performance Detail Report—We have updated the Application Performance Detail Report with sort parameters and the ability to suppress top offenders from the report. These changes are available on both the UI and on scheduled reports. The Sort Locations By parameter allows you to sort locations and top offenders by Violation Duration, Violation Count, Outages Duration, Outages Count, as well as alphabetically. You can suppress top offenders by setting the Show Top Offenders parameter to 0.
  • “Importance” property now included in Service Quality events—We now include an “Importance” property in SQA_EVENTs returned by the APM Event Integration feature.
  • Delay “Set monitoring point location” prompt—Previously, if you had a monitoring point whose location was not set, you’d be prompted to set it each time you logged on. Now, you have the ability to delay the prompt for a week. This enhancement applies to deployments with location services enabled.

Resolved issues

ID Keyword Description
APM-4750 Delivery We fixed an issue where, in some circumstances, the Routes pane would show routes properly when the Range was set to 1 hour or longer but would not show anything if the Range was set to 10 minutes.
APM-4640 Delivery We fixed an issue where hop labels on the Routes pane of the Network Paths page could not be added after the time Range changed.
APM-3935 Delivery We fixed an issue on the Routes pane where traceroutes originating from multiple predecessor networks to a common downstream network could overlap and only be seen when the downstream network was expanded.
APM-4388 Delivery We fixed an issue where, when too many network paths were configured on a monitoring point, the number of paths shown in the error message did not match the actual number of paths. In addition to the error message change, we have simplified the Manage Licenses page. Now, we only show the licensed WAN and Web path count and not the unlicensed path count.
APM-4863 Delivery We fixed an issue where the search function on the Network Paths page was unable to find some network paths by PathID or Name.
APM-1628 Delivery We fixed an issue where network path groups displayed on the Network Paths page using the Grouped By view could overlap one another.
APM-5296 Delivery We fixed an issue where the Path Template Group configuration page was slow when there were large numbers of monitoring points and interfaces available as Sources.
APM-4823 Delivery We fixed an issue where the Manage Path Template Groups page was slow to load for environments with large numbers of network paths.
APM-4369 Delivery We fixed an issue where the Tree Map could load slowly when there were a large number of network paths to display.
APM-2002 Delivery We fixed an issue where the timeline on the network path performance details page would not behave as expected with some OS/browser combinations (for example, iOS/Chrome 71).
APM-4370 Delivery We fixed an issue where a Supplementary Target (used when the primary target is not responding to ICMP) was not updating the corresponding Delivery path target.
APM-4787 Delivery/Experience We fixed an issue where, on the Delivery Events or Experience Events pages, if two text search terms were entered, only the last one would be used.
APM-4715 Events We fixed an issue where filters set on the Events page were still in effect after they were removed.
APM-1780 Groups We fixed an issue where creating or modifying a group using Manage Groups was not reflected on the Network Paths page. This issue was seen on IE11.
APM-4892 Voice/Video We fixed an issue where Voice/Video tests could fail to identify the target monitoring point if the target hostname contained upper case characters.
APM-4240 Diagnostics We fixed an issue where Diagnostic tests were not being initiated as expected when the test queue became full.
APM-4813 Diagnostics We fixed an issue where, for dual-ended paths, inbound diagnostics could be linked to outbound diagnostics resulting in odd and unexpected hop ordering.
APM-4293 Experience We fixed an issue where expanding/collapsing the DNS chart on the Test Timeline page within Experience monitoring caused the page to become unresponsive.
APM-3316 Experience We fixed an issue where the email notification for Experience alerts showed the URL of a violated milestone rather than the web path’s URL in the email summary.
APM-4904 Experience We fixed an issue where using the deep link from the Experience Events page took you to the current time rather than the time of the event.
APM-4820 Experience We fixed an issue where, when navigating away from then back to the Web App Groups page, all groups would be expanded.
APM-4973 Experience We fixed an issue where, when navigating away from then back to the Web App Groups page, we would remember whether “Expand all” or “Collapse all” was the last used and populate the page based on that. Now, whatever was expanded upon exit is expanded upon return.
APM-4960 Experience We fixed an issue where the Web Dashboard was not displaying data in collapsed view.
APM-5262 Usage We fixed an issue where the Deep Packet Inspection Interfaces page (accessed via Usage > Monitoring Points) could become unresponsive if the Show X entries field was set to “All”. We have removed the “All” option and have provided a “Filter Appliances” field to limit the number of Usage interfaces shown.
APM-4396 Licensing We fixed an issue where network paths could show as unlicensed even though there were licenses available for them to use.
APM-4533 User avatar We fixed an issue where, when a user avatar could not be found, an incorrect default avatar was displayed.
APM-3528 Organization summary We fixed an issue where the Organization Summary page could be extremely slow.
APM-3991 Alerts We fixed an issue where decimal values configured in alert profiles had the decimal part truncated on some screens.
APM-3561 SSO We fixed an issue where, when attempting to delete an organization, if it was associated with an SSO identity provider it would not be deleted, but there was no indication of this. We now display a message indicating that the organization must first be removed from the identity provider.
APM-4873 SSO We fixed an issue where SSO session logouts / timeouts redirected the user to /pvc/login.html, but this was not the appropriate login page for SSO users.
APM-2192 Audit log We fixed an issue where monitoring point removals were not shown in the audit log.
APM-5035 Monitoring Point We fixed an issue where monitoring points could show as online on the Manage Monitoring Points page even though they were offline.
APM-1170 Monitoring Point We fixed an issue where the Manage Monitoring Points page could show a private IP address in its Public IP Address field.
APM-5110 API We fixed an issue where the GET /v3/traceroute API endpoint could return an unexpected 500: Internal Server Error.
APM-5379 API We fixed an issue where the url attribute in the POST /v3/observer API endpoint could be a maximum of 255 characters. It can now be of any length.
APM-5120 API We fixed an issue where trying to specify two or more urls with different hostnames but the same domain in the POST /v3/observer API endpoint would not work. A message would be returned saying the urls needed to be unique.

Changes to be aware of

  • Configure Path Templates from the Network Paths they are associated with—Previously, the icon next to a network path on the Network Paths page provided a “Configure” option. Now, for network paths associated with a Path Template Group, the “Configure” option is replaced with “Configure Path Template”, providing a more direct way to edit the template.
  • Change to representation of repeated hops on Routes pane—A given hop can show up more than once on a traceroute for various reasons, including when tunnel (GRE) interfaces terminate on an interface and when NAT is performed at an interface. Previously, we counted these as separate hops and indicated it as a small loop on the Routes pane visual. This was confusing and was interpreted as a routing loop. Now, the hop is only counted once and the loop is removed from the visual. The repeated hops can still be seen in the route Export.
  • Experience workflow page cleanup—We have made style and interaction changes on the Experience workflow page to make it clearer and easier to use. For example, you can now add variables anywhere in the list of variables, not just at the bottom.
  • Help specifying the blacklist URL—When using the blacklist command in Selenium scripts, it was unclear that the URL argument should adhere to Chrome’s Match Pattern format. We now review the URL entered and, if it is not valid, we display an assistance message.
  • Change to clarify which alert profile is applied to a web path—We’ve made updates to the Alert Profiles column seen when creating or editing a Web App Group. The column indicates whether the path uses the alert profile specified in the workflow definition (used to say “Default”, now says “from workflow”), or whether the user has overridden that alert profile for that web path (used to say “Custom”, now says “path-specific”). It also indicates whether alerts are muted (“muted”) on the web path. In addition, the “default”, “custom”, and “off” radio buttons are replaced by a “Mute” button as the system now detects whether the web path uses the alert profile specified in the workflow, or overrides it with specific to the path.
  • Sorted alert profile list—Previously, the lists of alert profiles (both system and custom) were unsorted. Now, the lists are sorted alphabetically in the Web UI and in the API (via GET /v3/alertProfile).