Show search and navigation.

 

Custom Log File Format

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

The format in which data generated for CDN activity over the HTTP protocol is stored in a raw log file is determined by the settings defined in the Log Format Settings section of the Raw Log Settings page. These log file formatting settings allow you to:

Typically, data mining tools require a consistent log format when analyzing data over a period of time. If you plan on using a data mining application on your log data, then it is key to keep changes to your log file to a minimum. Please contact your CDN account manager before making any changes.

Base Log File Format

The base log file format determines the basic format that will be used to record HTTP activity in a raw log file. Once you have selected a base log file format, you can adjust other log file format settings (e.g., date/time format) to achieve your optimal log format. When choosing a base log file format, you will need to choose between the following two log file formats:

Key information about the combined log file format:

Date/Time Format

A CDN server records the date and time at which it processed the request for an asset in a log field called "timestamp." The format in which data is recorded in this field can be customized in one of the following ways:

Custom Field

By default, a custom field called "x-ec_custom-1" is included in your raw log files. This field will report "-" unless Rules Engine has been configured to log request/response header data. This type of configuration requires the use of the Custom Log Field 1 feature.

Changing the name of the custom field will not affect whether HTTP request and/or response headers are logged.

Raw log files that use the combined log format will not indicate the name of the custom log field.

When configuring the Custom Log Field 1 feature, specify the name of each request and response header that will be logged in that field. A header can be specified using the following syntax:

Header Type Syntax Example

Request

%{requestheader}i

%{Accept-Encoding}i

Response

%{responseheader}o

%{Content-Type}o

Key information about logging header data:

ClosedTo determine whether header information will be logged

  1. Navigate to the Raw Log Settings page. ClosedHow?From the main menu, navigate to Analytics | Raw Log Settings.

  2. Perform one of the following steps:

    • To log header information:

      1. Make sure that the Add this custom field to the log file option is marked. If desired, change the custom field name. Click Update if this step required a change to this setting.

      2. Navigate to the Rules Engine page corresponding to the platform for which header information will be logged.

      3. If a policy has not been deployed to the Production environment or does not contain the Custom Log Field 1 feature, then please create one that does.

        A copy of the policy currently deployed to the Production environment may be created. Modify the resulting draft to include the Custom Log Field 1 feature for the desired types of requests (e.g., Always). After which, convert the draft to a policy and then deploy it to the Production environment.

      4. Repeat the previous step for each desired platform.

      Append the appropriate identifier (i.e., i or o) to the header name to indicate whether you would like to log requests (inbound) or responses (outbound).

    • To exclude header data from the custom log field:

      1. Make sure that the Add this custom field to the log file option is cleared. Click Update if this required a change to this setting.
      2. Navigate to the Rules Engine page corresponding to the platform for which header information will be logged.
      3. Create a copy of the policy currently deployed to the Production environment.
      4. Remove all instances of the Custom Log Field 1 feature from the resulting draft.
      5. Convert the draft to a policy and then deploy it to the Production environment.

Content Access Point Logging

A content access point is a relative path that starts directly after the CDN hostname (e.g., /800001/MyOrigin or /000001). By default, this information is reported in the cs-uri-stem field in the log file. The cs-uri-stem field identifies the asset that was requested by the client. The Remove the content access point from the URL option determines whether this information is reported in that field.

Sample cs-uri-stem field values are provided below.