The latest update to mPulse resolves an issue that caused alerts to be delayed and/or misfired in some cases.

New features:

• Liveness tests with many headers. You can define multiple HTTP headers for any HTTP(S) liveness test configuration using the API and user interface.

• Disable liveness tests. You can use the API or a checkbox in the user interface to disable a liveness test, which directs the GTM service to cease running the test and effectively treat the test as no longer existing.

• Static property types. You can use the API to configure static answers, such as an A record value for GTM properties, to deliver static record responses.

• Apex properties. You can configure properties at the apex record of a domain, which eliminates the need to create a subdomain of a GTM domain with only one property. The API and user interface display the apex record with an @ symbol.

• Terraform Provider. You can use Terraform Provider to minimize the activity required to manage and configure GTM domains and properties.

With the latest update to mPulse, metrics that had been displayed as 9,999% will now correctly appear as 9.999%.

The latest update for API Gateway includes the following features and enhancements:

New features:

• JSON web token validation now support the use of an ‘iat’ claim.
• JWKS support allows for more seamless key rotations.
• Cache prefreshing is available for both RESTful and GraphQL-based APIs.

Enhancements:

• The API Endpoint Definition API returns only documented parameters.
• The ‘Reset to API settings’ button does not reset all of the settings in API privacy.
• The JWT public key validation includes a restriction to accept only the PKCS#8 format.

The latest update to mPulse includes the following bug fixes:

• Fixed an issue related to filters set in the dashboard property panel. Previously, the “do not display” filter setting did not persist on subsequent sessions.
• Fixed the animation of the Globe legend and resolved some issues that occasionally caused the Globe to crash on initial load.

The latest update to mPulse includes a change in frequency for uploading raw beacon data to Amazon S3, from 3 minutes to 5 minutes. This is a temporary measure we’re taking during holiday season in order to ensure real-time data in mPulse’s Waterfall tool.

The latest update to mPulse includes the following enhancement:

• mPulse Lite customers can now see and use the Dimensions dashboard.

The latest update to mPulse includes the following bug fixes:

• Fixed a chart permissions error that states: “Current user/tenant does not have permission to read object”. Previously, this error occurred if the widget permission was set higher than the dashboard level permission.
• Waterfall dashboard can now correctly filter beacons for synthetic browser values.
• mPulse Alert emails now include an image when that option is selected in alert Attributes.

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.

The latest update to mPulse includes the following enhancement:

• Single Page Apps (SPA) no longer require a specific framework selection in the ‘Configure your App’ dialog. Find out more about using Single Page Apps.

The latest update to mPulse includes the following bug fixes:

• The App Error List dashboard now displays the complete URL string.
• Fixed a race condition in dashboards that led to incorrect data display. Previously, incorrect data was displayed if a custom dimension filter was set at the dashboard level and a date/time filter was only present at the widget level.