CDN usage reports

Introduction

We provide a wide variety of CDN usage reports.

Reports

Reports of your bandwidth (you need to be logged in to access this page), traffic and costs. 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 and concurrent viewers (the latter for CDN Video and CDN Live services only). 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.

Advanced reports

Reports of CDN cache utilization and HTTP status codes.

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

You may have noticed that there are two types of data in our reports - Data Cached and Data Non-Cached.

Data Cached

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

Data Non-Cached

Data Non-Cached represents data requested by your end-users which were missing in the CDN cache. Please note that the data was automatically pulled from the origin server by the corresponding CDN edge server, then served to your end-user and then probably (see below) stored in the CDN cache.

Cache Hit Ratio

Cache Hit Ratio represents the following ratio in percents. 

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

Examples

Streaming CDN service

If you have a Wowza based streaming CDN service (CDN Video, CDN Video Push or CDN Live) then 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 still the traffic is (by design) 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 then it is missing in the CDN cache. If it is requested by your end-users via a CDN URL (or you prefetch it) then as explained above the content is automatically pulled from the origin server by the corresponding CDN edge server and then served to your end-users. Based on HTTP headers received from the origin server the content is or is not stored in the CDN cache (on 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 and 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 your content in the CDN cache expires (or if you purge it) then it is missing in the CDN cache and the situation is exactly the same as in the "New origin content" example above.

Redirect on Origin Domain

Let's assume that your Origin Domain (mycompany.com) redirects (3xx response code) to some other domain (for example to www.mycompany.com). Please note that in this case your CDN service will redirect to www.mycompany.com as well. It is expected behavior because CDN (by design) "mirrors" origin responses but it is typically not what you want because requests via CDN URLs will be served from your server via www.mycompany.com and you will not be using CDN at all. This traffic is counted as Data Non-Cached. Please note that to solve the "redirect problem" you need to 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 using cache control HTTP headers. In this case all traffic is counted as Data Non-Cached.



HTTP Status Codes

We provide reports of HTTP status codes: Real-Time Reports/HTTP status codes and Advanced Reports/HTTP status codes of HTTP responses for your CDN Static, CDN Static Push and CDN HTTP Live services. The following aspects are measured for your CDN service.

  • Number of 2xx status codes - Those status codes mean that the requests were successfully completed.
  • Number of 3xx status codes - Let's look at few examples.
    • 304 (Not Modified) - Means that your CDN content expired but the origin content was the same as in the CDN cache. In those cases we continue to cache your CDN content. In other words - everything is fine with those status codes.
    • 301 (Moved Permanently) - Means that the request was redirected to a different URL (in most cases to your origin). You should avoid redirecting to your origin because in those cases you are not using CDN. Usually the problem is caused by a permanent redirect on your origin server redirecting non www requests to www requests.
  • Number of 4xx status codes - Let's look at few examples.
  • Number of 5xx status codes - Those status codes are generated when there is a problem in communication between the origin server and the edge server. To minimize number of 5xx status codes we recommend to use CDN Static Push and CDN HTTP Live instead of CDN Static Pull as our storage servers have premium connection 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.

What next?

Read about the following topics.

Contact Us

 _    _      ___      _  __  
| |  | ||   / _ \\   | |/ // 
| |/\| ||  | / \ ||  | ' //  
|  /\  ||  | \_/ ||  | . \\  
|_// \_||   \___//   |_|\_\\ 
`-`   `-`   `---`    `-` --`