See Service for APM system status and upgrade schedule information.

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.

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 (due March 18, 2020) Monitoring Points or later. Also, double NATed paths only get back to the last NAT and require a manual override.

Resolved issues

ID Keyword Description
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”.