Akamai
Akamai DataStream 2 pushes log batches every 30 or 60 seconds to an S3 bucket managed by EINBLIQ.IO. A dedicated CMCD field records the player data.
Updated
Values provided by EINBLIQ.IO
| Value | Used for |
|---|---|
<BUCKET_NAME> |
S3 bucket |
<S3_ENDPOINT> |
Host name of the S3 storage endpoint |
<FOLDER_PATH> |
Folder path inside the bucket |
<BUCKET_REGION> |
Bucket region |
<ACCESS_KEY_ID> |
Access key ID for the bucket |
<SECRET_ACCESS_KEY> |
Secret access key |
Prerequisites
- Access to Akamai Control Center with permission to create DataStream streams and, if needed, to edit and activate properties.
- The delivery properties you want to include. The dedicated
CMCDfield is available for Adaptive Media Delivery properties.
Create the stream
- In Akamai Control Center, open Analytics & monitor → DataStream and select Create stream.
- Enter a display name, for example
EINBLIQ.IO, and choose the contract. - Under Include properties, select the delivery properties that serve your streams.
- If Akamai offers a DataStream-managed stream for your properties, use it: it needs no changes in Property Manager. Otherwise continue with a Property Manager-dependent stream and complete the property steps below.
Select the data set fields
On the data set page, select these fields and choose JSON as the log format.
| Field | Content |
|---|---|
| CMCD | CMCD values of the request |
| Request time | Request timestamp |
| Request host | Requested host |
| Request path | Path of the requested object |
| Query string | Query string of the request |
| Client IP | IP address of the client |
| Edge IP | IP address of the edge server |
| User-Agent | Client user agent |
| HTTP status code | Response status |
| Total bytes | Response size |
| Turnaround time | Time to serve the request |
| Transfer time | Time to transfer the response |
| Time to first byte | Time until the first response byte |
| Cache status | Cache hit or miss |
| Referer | HTTP Referer header |
| CP code | Content provider code |
| Error code | Akamai error code, if any |
Deliver to the S3 bucket
Select S3-compatible as the destination and enter the values provided by EINBLIQ.IO:
| Setting | Value |
|---|---|
| Display name | EINBLIQ.IO |
| Host | <S3_ENDPOINT> |
| Bucket | <BUCKET_NAME> |
| Path | <FOLDER_PATH> |
| Region | <BUCKET_REGION> |
| Access key ID | <ACCESS_KEY_ID> |
| Secret access key | <SECRET_ACCESS_KEY> |
| Push frequency | 60 seconds |
Select Validate & Save. Akamai checks the connection by writing a small verification file into the bucket, so that file in your first delivery is expected. Leave the remaining delivery options at their defaults, review the summary and activate the stream.
Enable the stream in Property Manager
Only Property Manager-dependent streams need these steps. In Content delivery → CDN → Properties, create a new version of each included property and add two behaviors to the rule that serves your media:
Log Request Details
| Setting | Value |
|---|---|
| Log Host Header | On |
| Log Referer Header | On |
| Log User-Agent Header | On |
| Log Akamai Edge Server IP Address | On |
| Log X-Forwarded-For Header | On |
DataStream
| Setting | Value |
|---|---|
| Stream version | DataStream 2 |
| Enable | On |
| Stream name | The stream you created |
| Sampling rate | 100 |
Save and activate the property version on production. If the stream was created inactive, also activate it in DataStream.
Keep CMCD out of the cache key
Add the Cache Key Query Parameters behavior to the same rule:
| Setting | Value |
|---|---|
| Behavior | Exclude only specified parameters |
| Parameters | CMCD |
| Exact match | Yes |
CMCD in headers
Players that send CMCD as headers, such as Apple AVPlayer, are covered by the same CMCD field. No additional custom log field is needed.
Check the delivery
DataStream pushes the first batch within a few minutes of activation. When the stream is active, inform EINBLIQ.IO. The delivery check then confirms that log files arrive with all fields and that the CMCD field is populated for your players.