Gcore

Gcore Logs Uploader exports CDN logs at an interval you choose to an S3 bucket managed by EINBLIQ.IO. CMCD headers can be logged with a FastEdge application developed by Gcore and EINBLIQ.IO.

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 inside the bucket
<BUCKET_REGION> Bucket region
<ACCESS_KEY_ID> Access key ID for the bucket
<SECRET_ACCESS_KEY> Secret access key

Prerequisites

  • Logs Uploader enabled for your Gcore 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, select Add target and choose S3 Other, the type for S3-compatible storage:

Setting Value
Protocol HTTPS
Endpoint <S3_ENDPOINT>
Access Key ID <ACCESS_KEY_ID>
Secret Access Key <SECRET_ACCESS_KEY>
Region <BUCKET_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.

Add these log fields to the policy:

  • body_bytes_sent
  • duration
  • host
  • http_referer
  • http_user_agent
  • http_x_forwarded_for
  • query_string
  • request_uri_path
  • server_addr
  • status
  • time_local
  • upstream_cache_status

Set the export interval to 5 minutes, the shortest interval Gcore offers.

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.

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 arrive in the same form. EINBLIQ.IO 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. When the configuration is enabled, inform EINBLIQ.IO. The delivery check then confirms that the files contain all fields and CMCD for your players.