Aug 29, 2022 — Stream ID and stream version as variables, stream ID as a data set, Postman collection available

  • Upload paths and log filename prefixes for object-based destinations now support the stream ID and stream version as variables. You can use this feature to group logs depending on the stream that gathers them. See Dynamic variables for details.

  • Stream ID is also the new data set field you can log in your stream for improved troubleshooting and sorting log files at your destination. Check Data set parameters for the complete list of data set fields you can log in DataStream 2.

  • The DataStream team has informed the Akamai account teams about customers with expiring feature entitlements, the impact on their streams, and possible next steps. If you wish to renew the entitlements, or want to check the status of your contract, please reach to your Akamai account team.

Aug 8, 2022 — Cloud Wrapper support

You can now use DataStream 2 to collect logs for the Cloud Wrapper (MultiCDN) product. Check the available data sets you can monitor in your CloudWrapper property in the DataStream application or the DataStream 2 API.

Jun 27, 2022 — New Relic support

  • Now you can choose New Relic as a destination to send log data in the DataStream application and the DataStream 2 API. As for other HTTP-based log streaming destinations, you can create properties with Akamaized hostnames to use as destination URLs for your streams and filter requests using IP access lists.

Jun 7, 2022 — Elasticsearch support, IP ACL and new data set fields

  • Now you can choose Elasticsearch as a destination to send log data in the DataStream application and the DataStream 2 API.

  • For HTTP-based log streaming destinations, you can create properties with Akamaized hostnames to use as destination URLs for your streams and filter requests using IP access lists. See custom HTTPS endpoint, Datadog, Elasticsearch, Loggly, Splunk, or Sumo Logic for details.

  • DataStream 2 now supports logging the Edge IP, Server country/region, and Billing region data set fields. Check Data set parameters for the complete list of data fields you can log.

  • You can log custom fields in DataStream 2 up to 128 bytes of data instead of 40 bytes. See Log custom parameters in the DataStream application or Custom log field in the DataStream 2 API.

Apr 11, 2022 — New migration tool and Open API V2 release

With the upcoming end of life of DataStream 1, we have released a new migration tool in the DataStream application you can now use to smoothly migrate your streams to DataStream 2. Check the DataStream user guide for details and migration options.

Mar 29, 2022 — Breadcrumbs data set field support

  • You can now use DataStream 2 to log breadcrumb data for improved visibility into the Akamai platform, using the new Breadcrumbs data set field for properties that belong to the Adaptive Media Delivery, Download Delivery, and Object Delivery products.

  • DataStream 2 now supports logging the Last byte data set field for properties that belong to Download Delivery products.

Mar 16, 2022 — Loggly destination support

Now you can choose Loggly as a destination to send log data in the DataStream application and the DataStream 2 API. See Stream logs to Loggly in the DataStream 2 user guide for details on to how stream log data to Loggly for improved data monitoring and analysis.

Mar 7, 2022 — Custom header and mTLS support

The Sumo Logic, Splunk and custom HTTPS endpoint stream destinations now support passing custom headers configured at these destinations. Check the DataStream user guide for each destination for details and configuration steps.

Feb 10, 2022 — Migration API tool release

With the upcoming decommissioning of DataStream 1 in mind, we have released a new API tool you can use to migrate your DataStream 1 streams to DataStream 2 individually or in bulk. Check the DataStream 2 API guide for details and migration options.

Dec 7, 2021 — EdgeWorkers data fields support

Now you can log data related to EdgeWorkers using a new data field group named EdgeWorkers information in DataStream 2.