Week of December 14, 2020 (APM 13.24.0)

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


  • Selected organization persisted across logins—For users with access to multiple child organizations as defined within your AppNeta Performance Manager account, we have added a small convenience for you. Rather than having to select an organization each time you log in, now, once it is selected, the organization persists until you change it. In most cases, this will save a step each time you log in.

Resolved issues

ID Keyword Description
APM-8430 CMP installation We fixed an issue where certain SSO users received “Access Denied” messages when downloading the Container-based Monitoring Point image.

Changes to be aware of

  • NMP 8.4.x and lower and all CMPs support only “External” upgrade mode—External upgrade mode (Upgrade Type column on the Monitoring Points page = “External”) means that a Monitoring Point cannot be upgraded from the Monitoring Points page. For these, “Upgrade Settings” and “Upgrade Now” actions (bulk and per Monitoring Point) are not available.
  • macOS NMP 12.x and later support only “Auto” upgrade mode—Monitoring Points that use the “Auto” upgrade mode check for upgrades periodically and upgrade themselves when new versions are available. Their upgrade mode and timing cannot be changed from APM.
  • Transition from Linux software sequencers—Linux software sequencers can no longer be created via the Add Monitoring Points workflow. Container-based Monitoring Points should be deployed instead.
  • Extended Experience script timeout—The maximum Experience script timeout has been extended from 60 seconds to testing interval / 3. This can be set via the APM UI when creating or editing a Web App Group or via the APM API (using /v3/webApplication/{id}). NOTE: Avoid setting an overly long timeout period. If the script does time out, it will consume resources on the Monitoring Point for the full duration of the timeout period.