medianova.comSupportLog in

Analytics

Static CDN is primarily used for delivering fixed content, such as images, CSS files, and JavaScript files. These resources are typically unchanged, which allows for faster delivery through a CDN. The Static CDN Analytics section provides key metrics that help monitor, analyze, and optimize the performance of static content delivery. These metrics focus on the caching effectiveness, the amount of traffic being served from the cache versus the origin server, and the overall bandwidth usage.

Traffic

  • Total Traffic: This chart displays the total amount of traffic delivered during a selected time range. Users can view the traffic over a custom time range or compare it with the previous time range to understand the trends and fluctuations in traffic. A significant increase in traffic indicates that the content is being accessed more frequently, which can be beneficial for scaling infrastructure and improving cache efficiency.

  • Traffic in Time: This chart provides insights into traffic variations over time. By analyzing traffic patterns, you can identify spikes in demand, possibly caused by promotions, seasonal events, or viral content. It also helps determine when content delivery peaks, assisting in optimizing server performance during high-traffic periods.

  • Cached vs Non-Cached: This chart compares traffic served from the cache versus traffic retrieved from the origin server. High cache traffic indicates that most of the data is being served efficiently from the CDN, reducing load on the origin server and speeding up delivery to end-users. A low cache hit ratio might indicate a need for better cache configuration or optimization.

  • Cached Data: This chart shows the breakdown of cached data into hits, updating, and stale categories:

    • Hits: Content successfully retrieved from the cache.

    • Updating: Content that is currently being updated in the cache.

    • Stale: Content served from the cache that is outdated because the origin server did not respond in time. These metrics are crucial for understanding cache freshness and the efficiency of the content delivery process.

  • Non-Cached Data: This chart shows the amount of data retrieved from the origin server, broken down into miss and expired categories:

    • Miss: Content that was not found in the cache and had to be fetched from the origin server.

    • Expired: Cached content that has expired and needs to be fetched again from the origin server. A higher proportion of non-cached data suggests that caching is not being utilized effectively, which could lead to higher latency and bandwidth usage.

Bandwidth

  • Bandwidth: This chart shows the total bandwidth used for delivering static content. High bandwidth usage might indicate large file sizes or a high volume of requests, which can be optimized through compression, better cache utilization, or content delivery strategies.

  • Cached vs Non-Cached: This chart compares the bandwidth used for cached versus non-cached data. Ideally, cached data should consume most of the bandwidth, as it reduces the need for repetitive fetching from the origin server, resulting in faster load times and reduced network strain.

Requests

  • Total Requests: This chart displays the total number of requests made for static content. A high number of requests indicates active content consumption, which is useful for monitoring content popularity and server load.

  • Hits vs Misses: This chart compares the number of requests that resulted in a cache hit versus a cache miss. A higher hit ratio is ideal, as it indicates that the CDN is effectively serving content from the cache, reducing the need to contact the origin server.

  • Request Hits: This chart shows detailed information on hits, broken down into hit, updating, stale, and revalidated categories:

    • Updating: The content is in the process of being updated.

    • Stale: The content is outdated and served while awaiting a response from the origin server.

    • Revalidated: The cached content has been successfully revalidated with the origin server and is now fresh. These metrics provide insights into the cache's efficiency and freshness.

  • Request Misses: This chart shows detailed information on misses, broken down into miss and expired categories:

    • Miss: The content was not found in the cache and was fetched from the origin server.

    • Expired: The cached content expired and had to be retrieved from the origin server again. Analyzing this data helps in understanding the reasons for cache misses and optimizing cache configurations.

Tier Filter

A Tier Filter dropdown is available next to the All Resources selector. This filter defines which CDN layers are included in the request data.

Option
Description

Edge only (default)

Displays requests from end users. Excludes internal CDN tiers.

All

Displays total requests from Edge + Mid + Origin layers. May include repeated counts of the same request across tiers.

Tooltips appear on hover for desktop and via an info icon on mobile. The selected filter is also reflected in exported reports.

Example report titles: Requests – Edge only Requests – All

API parameter: tier=edge or tier=all (default = edge)

Status Codes

  • Total Requests: This chart displays the total number of requests, helping you track overall activity and performance.

  • Status Code Structure: This chart compares the distribution of different HTTP status codes:

    • 2xx: Successful responses (e.g., 200 OK).

    • 3xx: Redirects (e.g., 301, 302).

    • 4xx: Client errors (e.g., 404, 403).

    • 5xx: Server errors (e.g., 500, 502). Monitoring these status codes helps identify potential issues in content delivery and client-side or server-side errors.

  • Successful Responses (2xx): This chart shows the distribution of successful responses, particularly focusing on the 200 OK code and other 2xx codes. High 2xx responses indicate that the CDN is successfully delivering content.

  • Redirects (3xx): This chart displays the distribution of redirect codes (301, 302, etc.). Redirects can indicate changes in content location, which should be minimized for optimal performance.

  • Client Errors (4xx): This chart shows errors on the client side, such as 403 (Forbidden), 404 (Not Found), and 429 (Too Many Requests). A high number of client errors suggests that users are requesting unavailable content or facing access issues.

  • Server Errors (5xx): This chart shows server-side errors, such as 500 (Internal Server Error), 502 (Bad Gateway), and 504 (Gateway Timeout). These errors indicate issues on the origin server and require attention to ensure smooth content delivery.

Tier Filter

Status code metrics also reflect the selected Tier Filter. You can view codes for Edge only or include All CDN tiers. When All is selected, totals may increase because the same request can appear multiple times across tiers.

Exported reports and visual charts indicate the active filter in their titles. API parameter: tier=edge or tier=all (default = edge)

Error Logs

Error logs provide a detailed record of requests that resulted in errors. By selecting a specific error code, users can view logs that include the request path, method, protocol, and hit status. The logs are invaluable for identifying patterns and resolving recurring issues in content delivery.

Tier Filter

The Tier Filter applies to all error log data. Users can toggle between Edge only and All, depending on whether they want to see only end-user–level errors or logs from all CDN layers.

Selecting Edge only isolates actual user errors, while All shows cumulative errors from Edge, Mid, and Origin.

API parameter: tier=edge or tier=all Default: edge

Last updated

Was this helpful?