Analytics

Streaming CDN is tailored for delivering video, audio, and live streaming content, which is often large and requires continuous, uninterrupted delivery to provide a smooth viewing experience. Streaming CDN ensures that users can access high-quality media content without buffering or delays, no matter where they are located. The Streaming CDN Analytics section helps monitor streaming performance, optimize delivery, and troubleshoot issues.

Traffic

• Total Traffic: This chart shows the total amount of streaming content delivered over a given period. It helps track how much video, audio, or live stream data is being consumed by users.

• Traffic in Time: This chart visualizes the traffic patterns over time, helping to identify peak usage periods when streaming content is being accessed the most. This data can be used to adjust delivery strategies to accommodate demand during peak times.

• Cached vs Non-Cached Traffic: Streaming content is often harder to cache effectively because it changes constantly. This chart compares how much of the streaming content is being served from the cache versus being fetched from the origin server. Ideally, caching strategies should be optimized to maximize cache hits for improved performance.

• Cached Data: This chart shows how much streaming content is being served from the cache, with categories for:

  • Hits: Successfully served from the cache.

  • Updating: Content that is being refreshed in the cache.

  • Stale: Content served from the cache that is outdated but still used temporarily. This helps understand how well the cache is handling streaming content.

• Non-Cached Data: This chart tracks the amount of streaming content that is being fetched from the origin server because it was not available in the cache. Non-cached content can lead to higher latency and bandwidth usage, so reducing non-cached content is a key optimization goal.

Bandwidth Analytics

• Bandwidth: This chart tracks the total bandwidth used for delivering streaming content. Streaming is typically bandwidth-intensive, so monitoring bandwidth is essential for optimizing the delivery and ensuring a smooth user experience.

• Cached vs Non-Cached Bandwidth: This chart compares the bandwidth usage for cached versus non-cached streaming content. High non-cached bandwidth usage indicates that more content is being fetched from the origin server, which could lead to delays or higher costs.

Requests

• Total Requests: This metric shows the total number of requests made for streaming content. It helps track how many users are requesting media and provides an overview of the content’s popularity.

• Hits vs Misses: This chart compares the number of requests that resulted in a cache hit (streaming content served from the cache) versus a cache miss (streaming content fetched from the origin server). A higher hit ratio is ideal, as it reduces the load on the origin server and improves delivery speeds.

Status Codes

• Total Requests: This metric tracks the total number of streaming content requests made by users.

• Status Code Structure: This chart shows the distribution of HTTP status codes for streaming content requests, which can help identify potential issues with content delivery. These 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 pinpoint where content delivery may be failing.

Error Logs

Error logs for streaming content provide detailed insights into issues related to specific media requests. These logs help identify and resolve any problems that might affect the viewing experience, such as buffering, missing content, or server-side failures.