Raw Logs Frequently Asked Questions

Raw logs provide historical information on the CDN traffic that flowed through your account. Each raw log contains platform-specific information for a given time period and location.

Although both raw logs and Real-Time Log Delivery generate log data, Real-Time Log Delivery provides log data in near real-time. Additionally, Real-Time Log Delivery is flexible with regards to the data that is collected and how it is delivered. Specifically, Real-Time Log Delivery allows:

• Log delivery to either AWS S3 or your web server.
• Downsampling of log data.
• Filtering for relevant log data. This reduces the amount of data that will be delivered, stored, and processed by your workflow.

Real-Time Log Delivery does not currently support the ability to report log data for custom fields defined within Rules Engine.

Learn more.

Yes.

It varies according to module.

Use the s-port column to determine the protocol used to request content. Typically, HTTP requests are over port 80, while HTTPS requests are over port 443.

The URI stored in the cs-uri-stem column will always start with "http://." This is a side effect of storing a URL as it was rewritten by our edge servers.

No. Raw log archival requires the following:

• Activation: The capability to archive logged CDN activity must be activated on a customer's account. For more information, please contact your CDN account manager.
• Setup: Raw log storage must be enabled on each desired platform.
• External Server: Optional. Deliver raw log files to your server by configuring delivery via SFTP.

There is no set frequency at which raw log files are generated.

Raw log files are generated and delivered as they are packaged by our servers. The frequency at which our servers package logged events for your customer account into a raw log file is determined by a series of factors, including the platform on which the event occurred and server load. As a result, the number and frequency of raw log files that will be delivered to your account cannot be predicted. If the interval between log packaging is long, then there will be fewer, larger log files. On the other hand, if this interval is short, then there will numerous, smaller log files.

Log files are typically delivered within 24 hours. However, it may take up to 7 days to receive all log files. The delivery of a raw log file may be delayed due to server maintenance.

Yes. The standard fee for storing content on CDN storage will be applied to your account.

The amount of time that raw log files will be stored in CDN storage is defined on the Raw Log Settings page.

Yes. Raw log files may be delivered to your server via SFTP.

Learn more.

Make sure that it allows access to the following subnetworks:

If a raw log file cannot be delivered to your server, then an email notification will be sent to the email address defined on the Raw Log Settings page. It is then your responsibility to transfer the raw log file to your server.

Raw log file delivery failures are not logged.

Raw log files are automatically stored in CDN storage for the length of time defined in your retention policy.

Your web administrator determines the retention period for all content stored on your servers.

• Content Delivery

  • ADN
  • IPv6
  • Cache Management
  • Rules Engine

• Security

  • CDN Security
  • MCC Security
  • Origin Shield
  • Rate Limiting
  • Token-Based Authentication
  • WAF

• Streaming

  • Dynamic Cloud Packaging
  • Smooth Streaming
• Raw Logs
• Route (DNS)
• Storage