Changelog

DataStream now natively supports IP-based access lists (ACLs) that use the same IP addresses as Origin IP access lists for the Akamai CDN.

DataStream now supports logging WebSocket data in delivery streams for properties with Ion Standard, Dynamic Site Accelerator, and API Acceleration.

DataStream 2 now supports logging GeoDelivery data fields in the Log information set: GeoDelivery Request Status and GeoDelivery Policy ID. These fields provide visibility for customer traffic served with active GeoDelivery policies, including exceptions where the requests were denied.

Starting now, you can choose to log the new TLS early data data field from the Message exchange data set in DataStream 2. Use this data set field to get metrics on sending client data to a server before the TLS handshake is complete.

You can choose the new Edge IP Binding status field from the Message exchange data set to log requests received through an Anycast IP and non-EIPB requests served directly from the edge server.

Starting now, you can choose Dynatrace as a qualified destination to send log data in the DataStream 2 application and the API.

Some Akamai contracts specify usage-based network surcharge for third-party provider traffic. DataStream 2 now logs this traffic using the Network provider field that returns the ID of the provider you may be surcharged for.

As of today, we're introducing the DataStream 2.1.1 General Availability (GA) release, which adds the support for the EdgeWorkers log type in the DataStream application and API.

Starting now, you can choose TrafficPeak for Hydrolix as a qualified destination to send log data in the DataStream application and the API.

We are thrilled to announce the General Availability (GA) release, adding support for DNS-related logs (eDNS and GTM logs) in DataStream.