Week of November 4, 2019 (APM 12.21.0)

See the service status page for AppNeta Performance Manager system status information.


  • 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.
  • 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.

Resolved issues

ID Keyword Description
APM-4715 Events We fixed an issue where filters set on the Events page were still in effect after they were removed.
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.

Changes to be aware of

  • 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).
  • Path Template Group error messages—We have updated the Path Template Groups page to display error messages when there are problems creating or modifying a path template group. Previously, the messages were not appearing on the Web UI.
  • 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.