Logging

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.

AnalyticsThis product provides a variety of reports that range from basic CDN usage statistics to real-time data to in-depth trend analysis on key metrics. This suite consists of the following modules: Core, Custom, Advanced Content Analytics, Real-Time Statistics, and Edge Performance Analytics. - Custom

The custom report capability must be activated on the desired types of requests before our servers will log the number of hits and the amount of data transferred for the requested criteria (e.g., edge CNAME). This differentiates it from other reports. As a result, it is important to consider the following notes:

For the purpose of generating custom reports, our servers will only log CDN usage data while the custom report capability is active for the desired types of requests. This means that data will not be logged for those requests prior to the activation date or after it has been deactivated.
A custom report can be generated for a time period that includes one or more dates on which logging for the desired type of request was not active. This will generate a report that contains partial or no usage data.
Custom report-specific logging for a particular type of request can be disabled at any time. This will not affect your ability to view historical data for the time period during which logging for that request type was turned on.
The Custom Reports module tracks hits and data transferred by cache status code and HTTP status code. This capability was introduced on 8/04/2015. Data collected before that date does not track cache status and HTTP status codes. Therefore, older data will only be reported in the Hits, Data Transferred, and the Unassigned fields.

The logging behavior described above only applies to the Custom Reports module. CDN usage statistics may always be viewed from one of our other reporting modules (e.g., Core Reports).