Gcore
Gcore Logs Uploader exports CDN logs at an interval you choose to an S3 bucket we manage. CMCD headers can be logged with a FastEdge application we developed with Gcore.
Last checked
Values you receive from us
| Value | Used for |
|---|---|
<BUCKET_NAME> |
Amazon S3 bucket |
<FOLDER_PATH> |
Folder inside the bucket |
<AWS_REGION> |
Bucket region |
<ACCESS_KEY_ID> |
Access key ID for the bucket |
<SECRET_ACCESS_KEY> |
Secret access key |
Before you start
Logs Uploader is enabled per account. If CDN → Logs → Logs Uploader is not available in your Gcore Customer Portal, ask Gcore support to enable it. Logs Uploader replaces the older Raw Logs export.
Add the S3 target
In Logs Uploader → Targets, create a target of type S3 Amazon:
| Setting | Value |
|---|---|
| Access Key ID | <ACCESS_KEY_ID> |
| Secret Access Key | <SECRET_ACCESS_KEY> |
| Region | <AWS_REGION> |
| Bucket | <BUCKET_NAME> |
| Folder | <FOLDER_PATH> |
The target shows Authentication complete once Gcore can write to the bucket.
Create the policy
In Logs Uploader → Policies, create a policy that defines the log fields and the export interval.
Include the fields listed in Log fields we need, including the query string, and set an export interval between 5 and 60 minutes. Shorter intervals make new sessions available sooner.
Connect target and policy
In Logs Uploader → Configurations, create a configuration that applies the policy and the target to the CDN resources that deliver your streams, and enable it.
Keep CMCD out of the cache key
In the cache settings of each CDN resource, open Query string and choose one of these options:
| Option | Effect |
|---|---|
Ignore only, with CMCD |
Removes only CMCD from the cache key |
| Ignore all | Removes every query parameter from the cache key (Gcore’s default) |
Changing the option can invalidate cached content, so apply it outside peak hours. Gcore’s secure token signs the path, not the query string, so the CMCD parameter does not affect token validation.
CMCD in headers
Gcore processes CMCD sent as a query parameter. For players that send CMCD headers, add the Log CMCD headers application from Gcore FastEdge to your CDN resource. It writes the CMCD headers into the cmcd log field in the same form as query-based CMCD, so both reach us identically. We developed the requirements for this application together with Gcore; read more in Full visibility for CMCD headers.
Check the delivery
The first files arrive after the first export interval. Tell us when the configuration is enabled; we confirm that the files contain all fields and CMCD for your players.