CDN usage reports

Introduction

We provide a wide variety of CDN usage reports which help you monitor bandwidth, traffic, costs, HTTP status codes and raw access logs for your CDN services. Depending on the type of report, you can review reports generated every hour, live reports generated every minute or real-time data available almost instantly. This allows you to analyze cache efficiency, redirects, status code distribution, current request activity and access logs, including raw access logs available for download or forwarding.

Reports

Reports of your bandwidth (you need to be logged in to access this page), traffic and costs. These reports are generated every hour. Please refer to Get CDN service reports for a documentation of API access to reports and for a detailed description of reports.

Live reports

The most recent reports of your bandwidth, traffic, concurrent viewers (the latter for CDN Video and CDN Live services only) and HTTP status codes. These reports are generated every minute. Please refer to Get CDN service live reports for a documentation of API access to live reports and for a detailed description of live reports.

Real time reports

Real time reports of your logs, top files, bandwidth, traffic and HTTP status codes served via the CDN. These reports are available almost instantly in real time.

Raw logs

For all CDN services we provide raw access logs. Please refer to Raw access logs for more details.

Data Cached vs. Data Non-Cached

Our reports distinguish between two types of traffic data: Data Cached and Data Non-Cached.

Data Cached

Data Cached represents data requested by your end-users and served directly from the CDN cache.

Data Non-Cached

Data Non-Cached represents data requested by your end-users that was not available in the CDN cache. In such cases, the corresponding CDN edge server automatically pulls the data from the origin server, serves it to the end-user and may then store it in the CDN cache for subsequent requests (see below).

Cache Hit Ratio

Cache Hit Ratio represents the following percentage. 

Data Cached / (Data Cached + Data Non-Cached)

Examples

Streaming CDN service

If you use a Wowza-based streaming CDN service (CDN Video, CDN Video Push or CDN Live), all traffic is counted as Data Non-Cached by design of our reports. In the case of CDN Video and CDN Video Push services, your videos are cached on CDN edge servers, but the traffic is still counted as Data Non-Cached. Please refer here for more details.


Please note that all remaining examples apply only to CDN Static, CDN Static Push and CDN HTTP Live services.

New origin content

When you add new content to the origin, it is initially missing from the CDN cache. If it is requested by your end-users via a CDN URL (or if you prefetch it), the corresponding CDN edge server automatically pulls the content from the origin server and then serves it to your end-users. Based on the HTTP headers returned by the origin server, the content may or may not be stored in the CDN cache on the edge server SSD drives for subsequent requests. In this case, the traffic from the CDN edge server to your end-users is counted as Data Non-Cached. The traffic from the origin server to the CDN edge server is not displayed in our reports and is free of charge.

Expired CDN content

When content stored in the CDN cache expires (or if you purge it), it is no longer available in the CDN cache and the situation is the same as in the "New origin content" example above.

Redirect on Origin Domain

Let's assume that your Origin Domain (mycompany.com) redirects with a 3xx response code to another domain, for example to www.mycompany.com. In that case, your CDN service will redirect to www.mycompany.com as well. This is expected behavior because the CDN mirrors origin responses by design, but it is usually not what you want, because requests made via CDN URLs will then be served from your server via www.mycompany.com and you will not be using the CDN at all. This traffic is counted as Data Non-Cached. To avoid this, make sure that your Origin Domain returns only 200 HTTP response codes.

Caching disabled on origin

Caching can be completely disabled on the origin server by using Cache-Control HTTP headers. In that case, all traffic is counted as Data Non-Cached.

HTTP Status Codes

We provide HTTP status code reports in Real-Time Reports/HTTP status codes and Live Reports/HTTP status codes for HTTP responses served by your CDN Static, CDN Static Push and CDN HTTP Live services. These reports measure the following aspects of your CDN service.

  • Number of 2xx status codes - These status codes indicate that requests were completed successfully.
  • Number of 3xx status codes - Examples include:
    • 304 (Not Modified) - Indicates that your CDN content expired, but the content on the origin was the same as the content already stored in the CDN cache. In such cases, the content continues to be cached.
    • 301 (Moved Permanently) - Indicates that the request was redirected to a different URL, in most cases to your origin. You should avoid redirects to your origin because in those cases the CDN is effectively bypassed. A common cause is a permanent redirect on the origin server from the non-www domain to the www domain.
  • Number of 4xx status codes - Examples include:
  • Number of 5xx status codes - These status codes are generated when there is a problem in communication between the origin server and the edge server. To minimize the number of 5xx status codes, we recommend using CDN Static Push and CDN HTTP Live instead of CDN Static Pull, because our storage servers have premium connectivity to our edge servers.
  • 2xx Ratio - Ratio 2xx / (2xx + 3xx + 4xx + 5xx)

Please refer to Status Code Definitions or List of HTTP status codes for more details.

A note on Cache Hit Ratio

In Live Reports/HTTP status codes, Cache Hit Ratio is calculated as the number of HTTP responses served from the CDN cache divided by the total number of HTTP responses. Unlike the Cache Hit Ratio in bandwidth and traffic reports, this ratio is based on the number of responses rather than on the volume of transferred data. Depending on the size of individual responses, the ratios may be similar or may differ.

What next?

Read about the following topics.

Contact Us

           __   __    ______  
    ___    \ \\/ //  /_____// 
   /   ||   \ ` //   `____ `  
  | [] ||    | ||    /___//   
   \__ ||    |_||    `__ `    
    -|_||    `-`'    /_//     
     `-`             `-`