The Metrics

Details about the tracking of CDN bandwidth and other metrics.

CDN Bandwidth

This is the metric that determines if you will go over your monthly alloted capacity.

Any time an asset is requested, CDN will be the entry point.

CDN can then determine if the asset has been previously requested, and therefore, serve it immediately.

The served asset will be the optimized version, with the requested transformations applied.

In case the asset has not been cached, the request will hit the ixmage service where the source image will be optimized and served.

Note that the bandwidth tracked will be the size of the optimized image and not the size of the source image.
In other words, if your source image is 4MB in size, but you use a version in your markup that is 200x200 pixels, that may come out to be of size 100kb, as an example, and this is the amount of bandwidth that is considered towards your limit.

Requests that have been cached will not count towards the Transformations (XFs) metric.

Refer to this CDN Article to learn about CDN invalidations.

Other Tracked Metrics

XFs Transformations

An XF (transformation) is a request that will require processing the source image into a new optimized variant.

You can add any number of image transformations to the request, like width, height, quality, all these are part of the same XF.

XFs are cached to include the transformations from the querystring.

This metric is not considered for your monthly limits.

Invalidations

An invalidation is a request to eliminate one or more cached assets in the CDN.

From within your Control Panel’s Dashboard, you have the ability to invalidate a single image url, or a set based on how your images have been grouped in folders and aliases. For more information on how to invalidate, refer here.

This metric is not considered for your monthly limits.

Hitting the Limit

If your monthly usage goes over your plan alloted bandwidth, the service will start putting a watermark on your requests.

Here are a couple of examples: