Change to CDN Edge Time Calculations

Effective July 23, 2019, mPulse’s CDN Edge Time calculations, such as All Asset CDN Edge Time, are calculated differently.

Prior to this change, Edge Time calculations rounded down. For example, 0.1 ms was rounded down to 0 ms. Now, Edge Time calculations round up. For example, 0.1 ms will round up to 1 ms. This affects mPulse as data with the value of “0” is not included in charts, tables, or median calculations. Sites with many Edge Times rounding down to 0 ms would have had those data points excluded, which skews reporting by only including data with a value over 0.5 ms.

Prior to this change, if you had many reported 0 ms Edge Times, you might see a reduction in their median Edge Times going forward, since the faster data points will now be included as 1 ms.

The latest update to mPulse includes the following bug fix:

• Re-enabled the capability to add multiple domains in the mPulse session tracking UI without requiring a cross domain tracking URL.

The latest update to mPulse includes the following bug fix:

• Mobile beacons are now counted properly for Akamai Billing Center.

Changes, enhancements, and bug fixes

Changes and Enhancements:

• A new charting library, resulting in improved chart performance and some very minor styling updates.
• The ability to set a separate axis title for combined metric charts.
• Improved handling of domain filters in widgets.
• Dashboard y-axis setting now persists when you close and reopen.
• Time series charts are now anchored at zero (0) by default.
• In the Specify Alert Detail dialog, the add an annotation checkbox label now reflects that auto cleared alerts won’t trigger annotation generation.

Bug Fixes:

• An issue with size bucket values. 
• An issue that was causing falsely triggered alerts.
• Inconsistencies between error messages when adding new custom timer charts in dashboards.
• An issue where the browser would become unresponsive when exporting to image is selected from a pop-out widget.
• An issue with median values for mPulse Decoded Body Size.
• An issue with beacon counts in the Multi-dimension table widget.
• An issue with incorrect y-axis values for the Static Max Value metric.
• An issue where custom metrics were only visible across widgets when filtering to one day.

Bug fix for mPulse auto-app creation feature

A component in the recent Property Manager (19.3) release and mPulse auto-app creation feature had a bug. Each time a new version of a RUM-enabled property only was changed, a new mPulse app was automatically created. mPulse auto-app creation should happen only when a change to an existing property has the mPulse behavior enabled. In this release, mPulse apps were automatically created whether the property configuration version had the mPulse behavior enabled or not.

To address the issue, the component that caused the bug has been rolled back, which prevents the auto-creation of a new mPulse app when a change is made to an existing property that does not have the mPulse behavior enabled. With this rollback, new mPulse apps are automatically created only when the mPulse behavior is added to the property configuration and the API Key field is left blank.

The latest Adaptive Acceleration release includes the following enhancements and bug fixes:

• Added Automatic Font Preload to the optimizations provided by Adaptive Acceleration. Font Preload allows the CDN edge server to determine the most important fonts using beacon data. These fonts are then identified with a response header so they can be downloaded before the browser has processed the base request. Display of font preloads will be available on control.akamai.com on June 18. Customers will be able to toggle the feature on and off starting on June 25.
• Policies using the mPulse data source will now respect the push/preload toggles in the Adaptive Acceleration behavior.
• A bug that prevented customers from getting policies when sending synthetic traffic to their properties (with tools like WebPageTest) has been fixed. Sites that only receive synthetic traffic should now receive more pushes, preconnects, and font preloads.

Updates to mPulse and Real User Monitoring (RUM)

The latest Property Manager release includes the following changes for RUM customers:

• For new properties, the mPulse behavior is automatically turned on in the property configuration with a default (blank) mPulse app API key. Leaving this mPulse API key blank automatically creates a new mPulse app that corresponds to the property. After the property is active on the Akamai production network, all of your data (beacons) are directed to your mPulse app. mPulse replaces all product templates that previously had RUM as the default behavior with mPulse (with the default API key).

• If you have RUM on an existing property, and wish to use mPulse, remove the RUM behavior from the property.

• RUM and mPulse should not coexist on the same property. If you choose to use both RUM and mPulse, you need to explicitly provide an API key for the mPulse behavior. To locate the API Key of an existing mPulse app, log in to mPulse, select the mPulse app from the Home page, then click the General tab to view the API Key.

Script Management Opt-In Service Worker Updates

The Service Worker served on a particular domain only updates with the latest version of the Akamai Script Management Service Worker in either of the following two instances:

• When a new version of the Property Manager configuration associated with that domain (and with the Script Management behavior enabled) activates.
• When a new version of a Script Management policy publishes within the Script Management application.

Note: The previously released SPOF reporting feature requires that you use a minimum Boomerang version of 1.621.0 as part of mPulse data collection.

Script Management Adds Analysis Mode Support

• Added Analysis Mode Support in which a Service Worker does not install, but the information regarding the scripts served on a domain is still analyzed and displayed in the Script Management UI.  Analysis mode is set within the Script Management behavior in Property Manager. This provides customers with a “visibility” mode.
• Safety improvements to Service Worker. Service Worker acts on script requests only and does not handle any other type of request.
• Added Support for Safari Mobile.  To enable this, you must update the Property Manager behavior to install the Service Worker on Safari Mobile.
• SPOF Protection events are collected and reported in the Script Management UI. This includes the number of SPOF actions in the last month, and the first and last time the SPOF action occurred in that timeframe.

The latest update for API Gateway includes the following enhancements:

• The property activation status check is now functional.
• Endpoint versions may now be updated when any associated hostnames have been removed from property configurations but remained in use in API configurations.
• Performance improvements in backend configuration processing.
• GraphQL users may now specify a maximum query size up to 8129 bytes.
• GraphQL users may now specify a nesting depth for queries up to 100 levels.