Hydrolix and Akamai TrafficPeak
If your CDN logs already flow into Hydrolix or Akamai TrafficPeak, EINBLIQ.IO queries the log table directly. No S3 bucket and no per-CDN setup are needed.
Updated
How it works
EINBLIQ.IO reads your CDN logs from the Hydrolix table in which they are already collected and normalised. Instead of delivering log files, you give EINBLIQ.IO read access to that table, and EINBLIQ.IO queries it through your cluster’s endpoint. The same applies to Akamai TrafficPeak.
Because the table already combines the logs of every CDN that feeds it, no separate setup per CDN is required.
Values you provide to EINBLIQ.IO
| Value | Description |
|---|---|
| Cluster endpoint | Address of your Hydrolix or TrafficPeak cluster |
| Table name | Project and table that hold your CDN logs |
| Bearer token | Token with read access to that table |
Create the token for an account that can only read this table, and provide it to EINBLIQ.IO.
Prerequisites
- CDN logs in a Hydrolix or TrafficPeak table that contains the required log fields, including the full query string. Column names can follow your schema; they are mapped during onboarding.
- Permission to create an account and token with read access to that table.
CMCD in your CDN logs
CMCD reaches the table through your CDN logs. Configure your players to send CMCD as a query parameter, and keep CMCD out of the cache key in your CDN configuration, as described in the guide for your CDN.
Check the connection
When EINBLIQ.IO has the three values, a test query confirms that the table is reachable and contains all required fields and CMCD for your players.