Guide
TrainingSupportCommunity

Cloud Wrapper reports

Suggest Edits

Cloud Wrapper reports let you see near real-time and historical data on the traffic assigned to your Cloud Wrapper configuration. You can access the reports from the Reports menu. See How to use reports.

Cloud Wrapper Multi CDN Realtime report

The Multi CDN Realtime report gives you near real-time data on your Cloud Wrapper configuration, including hits, volume, and time to first byte performance via other content delivery networks (CDNs). You can view the data with a maximum latency of 15 minutes.

📘

This report only provides data for Cloud Wrapper configuration performance via third-party CDNs. To see ​​Akamai​ network performance, see the standard Realtime report.

Data retention and granularity
This report shows data for up to the last 30 days.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • Cloud Wrapper Config (required). The Cloud Wrapper configuration to generate the report for.

  • Product Type (optional). The product to be included in the report. You can select AMD Live, AMD VoD, or Object Delivery.

Metrics

  • Hits. All hits to your Cloud Wrapper configuration from clients through third-party CDNs, during the date and time range you selected.

  • Hits/Sec. Hits per second from third-party CDNs, during the date and time range you selected.

  • Volume. The amount of data served from your Cloud Wrapper configuration's cache to requesting third-party CDNs, for the date and time range you selected.

  • Bandwidth. The average bandwidth of data transferred between your Cloud Wrapper configuration's cache and requesting third-party CDNs, for the date and time range you selected.

  • Time to First Byte (TTFB). Shows the responsiveness of your Cloud Wrapper configuration cache. It measures the amount of time it takes to deliver the first byte of content from this cache to a requesting client, via third-party CDNs. The report shows the average TTFB for your content over the date and time range you selected.

  • 2xx Hits. Number of hits that returned response codes - 200 to 299 (Successful).

  • 3xx Hits. Number of hits that returned response codes - 300 to 399 (Redirection).

  • 4xx Hits. Number of hits that returned response codes - 400 to 499 (Client Error).

  • 404 Hits. Number of hits that returned response code - 404 (Not Found).

  • 429 Hits. Number of hits that returned response code - 429 (Too Many Requests).

  • 5xx Hits. Number of hits that returned response codes - 500 to 599 (Server Error).

Cloud Wrapper Multi CDN Historical report

The Multi CDN Historical report lets you see your Cloud Wrapper configuration's past cache space and offload performance, over multiple content delivery networks (CDNs). It shows you an end-to-end analysis of offload from edge to origin and lets you see the effectiveness of your Cloud Wrapper configurations.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • Cloud Wrapper Config (required). The Cloud Wrapper configuration to generate the report for.

  • Traffic (optional). HTTP traffic to be included in the report data.

    • All Responses. Includes all response traffic.

    • GET Head Responses. Response header traffic from GET operations.

    • PUT POST Requests. Request traffic from PUT and POST operations.

    • PUT POST Responses. Response traffic from PUT and POST operations.

  • Delivery Type (optional). Distinguishes secure traffic from non-secure traffic.

  • IP Version (optional). Supported array values are IPv4 and IPv6. If no IP version is selected, the report shows data for both IPv4 and IPv6.

Metrics

  • Hits/Sec. Hits per second from third-party CDNs, during the date and time range you selected.

  • Bandwidth. The average bandwidth of data transferred between your Cloud Wrapper configuration's cache and requesting third-party CDNs, for the date and time range you selected.

  • 2xx Hits/Sec. Number of hits per second that returned response codes - 200 to 299 (Successful).

  • 3xx Hits/Sec. Number of hits per second that returned response codes - 300 to 399 (Redirection).

  • 4xx Hits/Sec. Number of hits per second that returned response codes - 400 to 499 (Client Error).

  • 404 Hits/Sec. Number of hits per second that returned response code - 404 (Not Found).

  • 429 Hits/Sec. Number of hits per second that returned response code - 429 (Too Many Requests).

  • 5xx Hits/Sec. Number of hits per second that returned response codes - 500 to 599 (Server Error).

Cloud Wrapper Historical report

The Historical report lets you see your Cloud Wrapper configuration's past cache space and offload performance, on the ​Akamai​​ CDN. It shows an end-to-end analysis of offload from edge to origin and lets you see the configuration's effectiveness.

Filters

  • Cloud Wrapper Config (required). The Cloud Wrapper configuration to generate the report for.

Metrics

  • Origin Offload (Hits). The average percentage of hits from edge servers as compared to the hits from your origin server, for the filtered time range, with and without Cloud Wrapper.

  • Origin Offload (Volume). The average percentage of bytes delivered from edge servers as compared to the bytes delivered from your origin server for the filtered time range, with and without Cloud Wrapper.

  • Average Fetches Per Object. The average number of fetches per object to your origin server, for the selected Cloud Wrapper configuration, in the filtered time range. ​Akamai​ aims for approximately 1-1.5 for average fetches per object. (This is not a service level agreement). If Average Fetches per Object increases, ​Akamai​ will consider increasing your footprint. It is usually an indicator that your footprint's cache space isn't large enough to hold both your popular and your long-tail content.

  • Offload (Hits). The average percentage of hits to ​​Akamai​​ edge servers as compared to the hits to your origin server, for the filtered time range, with and without Cloud Wrapper. This is calculated as follows: (Egress Hits - Cloud Wrapper Hits) / Egress Hits * 100.

  • Offload (Volume). The average percentage of bytes delivered from edge servers as compared to the bytes delivered from your origin server, for the filtered time range, with and without Cloud Wrapper. This is calculated as follows: (Egress Bytes - Cloud Wrapper Bytes) / Egress Bytes * 100.

  • Origin Hits. Number of all hits to your origin servers from end users for the chosen duration, with and without Cloud Wrapper.

  • Origin Hits/Sec. Number of origin hits per second for the chosen time duration, with and without Cloud Wrapper.

  • Origin Volume. The amount of data served by your origin for the given time duration, with and without Cloud Wrapper.

  • Origin Bandwidth. The average bandwidth of the data served by your origin for the given time duration, with and without Cloud Wrapper.

  • Average Fetches Per Object. Compares the average number fetches to your origin server versus the number of hits to your Cloud Wrapper configuration, for the same object.

Cloud Wrapper Realtime report

The Realtime report gives you near real-time data on your Cloud Wrapper configuration, including hits, volume, and offload performance. You can view the data with a maximum latency of 15 minutes.

Data retention and granularity
This report shows data for up to the last 7 days.

Filters

  • Cloud Wrapper Config (required). The Cloud Wrapper configuration to generate the report for.

Metrics

  • Origin Hits. Number of all hits to your origin servers from end users for the chosen duration, with and without Cloud Wrapper.

  • Origin Hits/Sec. Number of hits to your origin per second, for the given time duration, with and without Cloud Wrapper.

  • Origin Volume. The amount of data served by your origin for the given time duration, with and without Cloud Wrapper.

  • Origin Bandwidth. The average bandwidth of data served by your origin, for the given time duration, with and without Cloud Wrapper.

  • Unique Cache Space. You're assigned a set cache space for your Cloud Wrapper configuration, and ​Akamai​​ replicates it to meet the demand for your content. This metric denotes the unique cache space that was actually used by your content, over the time specified.

  • Unique Objects. You're assigned a set cache space for your Cloud Wrapper configuration, and ​Akamai​​ replicates it to meet the demand for your content. This metric denotes the unique count of objects that were cached, over a time specified.

  • Approved Object Limit. An object count limit assigned to your configuration, based on the Cloud Wrapper quota space chosen during provisioning.

Updated about 1 year ago