Analytics

Dynamic CDN is specifically designed for delivering content that is generated in real-time, such as personalized web pages, API responses, or dynamic data that changes based on user interactions or other real-time factors. Unlike static content, which remains the same across all users, dynamic content is customized and often updated frequently, making caching more complex. Dynamic CDN Analytics focuses on optimizing the delivery of this content while ensuring low latency and minimal server load.

Traffic

• Total Traffic: This metric shows the overall amount of traffic served by the CDN for dynamic content over a selected period. Dynamic content typically consumes more resources because it is generated on-demand, so monitoring this traffic helps track how much data is being delivered to end users.

• Traffic in Time: This chart visualizes the fluctuations in traffic for dynamic content across different times. By understanding the time periods when traffic spikes, you can adjust your infrastructure and caching policies to accommodate demand during peak periods.

• Cached vs Non-Cached Traffic: In dynamic content delivery, the cache hit ratio is typically lower than static content, since the content is personalized and frequently updated. This chart shows how much of the dynamic content is served from the cache versus directly from the origin server. Higher cache hits lead to better performance and reduced strain on the origin server.

• Cached Data: This metric tracks the efficiency of the cache for dynamic content. It is broken down into:

  • Hits: Content served from the cache without needing to fetch it from the origin server.

  • Updating: Content that is in the process of being updated in the cache, reflecting new changes.

  • Stale: Content that has expired or is outdated but is served temporarily while the cache is being updated. Optimizing cache utilization is crucial for improving performance, especially for dynamic content.

• Non-Cached Data: This shows the volume of dynamic content that had to be fetched from the origin server because it wasn’t available in the cache. The non-cached data is further categorized into:

  • Miss: Content that wasn’t found in the cache and had to be fetched from the origin.

  • Expired: Content that expired in the cache and needed to be re-fetched. Reducing non-cached data can significantly improve performance and reduce latency.

Bandwidth

• Bandwidth: This chart shows the total bandwidth used to deliver dynamic content. Dynamic content is often more bandwidth-intensive because it is personalized or generated in real-time. By tracking bandwidth, you can identify if there are any bottlenecks or areas where optimization is needed.

• Cached vs Non-Cached Bandwidth: This chart compares the bandwidth used for cached dynamic content versus non-cached content. If a large portion of bandwidth is being used for non-cached content, it indicates that caching could be optimized to reduce the load on the origin server and improve overall performance.

Requests

• Total Requests: This metric shows the total number of requests made for dynamic content. A higher number of requests indicates more frequent user interactions, which may require adjustments to the caching strategy and infrastructure to maintain performance.

• Hits vs Misses: This metric compares the number of requests that resulted in a cache hit (the content was found in the cache) versus a cache miss (the content had to be fetched from the origin server). Dynamic content typically has more misses than static content, but tracking this ratio is essential for understanding how well the caching strategy is working.

• Request Hits: This chart breaks down the cache hits into:

  • Hit: The content was successfully served from the cache.

  • Updating: The content is being updated and served from the cache while it’s in transition.

  • Stale: The content is outdated but still served from the cache until a fresh version is available.

  • Revalidated: The content was successfully revalidated with the origin server and is fresh again. These metrics help in understanding the freshness and effectiveness of the cache for dynamic content.

• Request Misses: This chart shows the breakdown of cache misses, with categories for:

  • Miss: Content not found in the cache, requiring a fetch from the origin server.

  • Expired: Cached content that has expired and needed to be fetched again. Optimizing cache policies can help reduce the frequency of misses and expired content.

Status Codes

• Total Requests: This chart shows the total number of requests for dynamic content. It’s a general indicator of how much dynamic content is being consumed by users.

• Status Code Structure: This chart breaks down the HTTP status codes for dynamic content requests, which helps monitor the success or failure of content delivery. The status codes include:

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

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

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

  • 5xx: Server errors (e.g., 500 Internal Server Error). Monitoring these status codes helps identify any potential issues in content delivery, such as missing content or server failures.

• Successful Responses (2xx): This chart shows the number of successful responses (e.g., 200 OK) to dynamic content requests. A high percentage of successful responses indicates that the content is being delivered properly.

• Redirects (3xx): This chart tracks the number of redirects (e.g., 301, 302). Redirects may be needed when content is moved to a different location, but too many redirects can cause delays and impact performance.

• Client Errors (4xx): This chart tracks client-side errors, such as 404 (Not Found) or 429 (Too Many Requests). These errors indicate that the client made a request for content that is unavailable or improperly requested.

• Server Errors (5xx): This chart tracks server-side errors, such as 500 (Internal Server Error) or 502 (Bad Gateway). Server errors indicate issues with the origin server, which need to be addressed to ensure proper content delivery.

Error Logs

Error logs for dynamic content provide detailed insights into requests that resulted in errors. This can help identify patterns, such as specific URLs that frequently cause issues, or issues that occur at particular times, helping to resolve any underlying problems.