CDN statistics

You can view your CDN statistics for an active domain in a content delivery server.

You must register a domain in the cockpit. If you haven’t done that, see Domains and Certificates.
The statistics sections remain empty until you enable a domain for the content delivery server.

View stats

  1. Go to Content delivery > Statistics.

  2. Select the desired domain from the dropdown list.

  3. Select the Date Range for the statistics.

    stats choose filters
Table 1. Available statistics
Statistic Description

Hit Ration

Rate of hits over all requests per second in the last hour.

Hits

Requests per second with hit cache status in the last hour.

Miss

Requests per second with miss cache status in the last hour.

Miss Time

Requests per millisecond with miss cache status in the last hour.

Requests

Requests per second in the last hour.

Errors

Requests per second with error cache status in the last hour.

GRAPHS

Requests graph

Number of requests over a selected time range.

Bandwidth graph

Number of bytes transmitted over a selected time range.

Global POP Traffic

The global Point of Presence (POP) traffic over a selected time range. These are the key access points from which the CDN delivers its service.

For more, see POP network.

Purge CDN

To purge the entire cache from the content delivery server for the domains in the selector, click Purge CDN. Alternatively, you can purge by URL.

For more, see Purging.
purge cdn
It does not currently purge your magnolia instances cache.

Purge URL

Instead of purging the entire cache, you may want to simply purge a single object from all cache servers. In this case, you will want to use the Purge URL option in the Cockpit.

Instructions

  1. Go to Content delivery > Statistics.

  2. Under CDN Actions, click Purge URL.

    purge url

  3. In the dialog:

    1. Choose your desired Domain from the dropdown list.

    2. Enter the Full URL path of the object that you want to purge.

    3. Optionally select to perform a Soft purge.

      If unselected, a hard purge is performed which immediately makes the object inaccessible. Soft purges mark the object as stale, but it is still accessible.

      Stale objects can reduce backend loads by allowing for conditional revalidation and other performance-enhancing patterns. For more, see Fastly’s soft vs hard purge docs.

    4. Click Purge URL.

      purge url dialog

Feedback

PaaS