We’re excited to announce the expansion of EdgeWorkers to Akamai’s enhanced secure network. You can now run edge functions everywhere on the network. Other notable changes include our new EdgeWorkers Management application and the Command Line Interface (CLI).

Note: If you have EdgeWorker functions deployed under the Tech Preview, there are changes below which will require a code update. Future releases will not force immediate code changes.

New:

• You can now perform the administrative tasks required to execute EdgeWorkers functions with the EdgeWorkers Management application user interface (UI).
• The EdgeWorkers CLI is now available to help automate and simplify your workflow.
• Trace response headers are now available to debug code on the network.
• The Cookies and URLSearchParams modules are available to access and modify query parameters.
• JavaScript modules can now be combined in the“main.js” file, allowing you to include useful libraries or align code to different teams.

Updates:

• The “main.js” file is now a module, enabled in strict mode by default. The four event functions now require the “export” keyword.
• The Request and Response Object methods have been removed from the new Cookies module.
• The Response constructor has been removed.
• The userLocation object now includes zipcode and city.
• onOriginRequest() and onClientResponse() cannot be used to create responses.
• When creating a deny response, you can provide the reason using the Reason ID.
• EdgeWorkers is now enabled across Akamai’s enhanced secure network. You no longer need the custom map to limit your traffic to a specific edge machine.

The latest update for API Gateway includes the following features:

• In JWT settings, you can now load public RSA keys dynamically from a JSON web key set (JWKS).
• The color of switches throughout the API Definitions and Key and Quota Management applications has changed from red/green to grey/dark blue to increase usability.

New features:

• New UI ergonomics. Uses Akamai’s new reporting framework.

• Improved SLA workflow. Enables you to easily monitor SLA service availability and align with SLA terms.

• GTM CLI. Enables a GTM CLI package for the Akamai CLI client.

The latest update to mPulse includes the following bug fixes:

• TLS Handshake time is now available in dashboards.
• Alerts can now call a webhook address that contains the & character.

The latest update to mPulse includes the following feature:

• There are new API endpoints for Dimension-Over-Time and App-Error-Summary, as well as enhancements for Metrics-By-Dimension. Find out more about the mPulse Query API.

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.