Observability

CloudFront Invalidation Metrics

By Karl Hepworth23 June 2022

CloudFront plays a crucial part in getting content to users after you publish it, and we wanted Skpr customers to be able to understand the impacts of purging its cache.

So, in a recent release of Skpr, we shipped metrics for monitoring CloudFront Invalidations from your applications' CloudWatch dashboard.

What are invalidations?

Invalidations are user-created requests to purge the cache for one or more paths.

Purging content is usually triggered from the application - so that when content is updated, a user can see it immediately. Inversely, the same process can be used to remove sensitive content from production.

Skpr customers can also use the command line to create these invalidation requests outside application automation.

What invalidation metrics are available?

We've recently added CloudFront Invalidations to our application dashboards. This provides customers with greater oversight of application patterns and behaviour.

Diagram demonstrating workflow of cache invalidations

There are two metrics available. These are updated every five minutes:

  • Total count of invalidations
  • Total paths invalidated

Screenshot of CloudWatch dashboard widget showing an example data-set and the relationship between request count
and invalidation path count.

What can I do with this data?

CloudFront Invalidation metrics place control in the hands of developers. Invalidations can be triggered manually via the command line, your project, or a manual entry in the AWS console, and these metrics are a consolidation of this information.

This data can indicate interesting behaviour in an application:

An error with automation

As an example, you may have several requests created by the application. You would then be able to see if the invalidations were in line with expectations or if your application sends too many (or not enough) requests.

Information isn't available

If expected data is missing or a block of time is missing, this may indicate an error with another process that didn't purge the cache as you expected. More significant releases tend to spike invalidation paths, and the data will reflect this.

Potential cost optimizing

Cost is based on how many paths have been purged. The key is being able to identify any problems that have occurred.

If there are issues, you have the opportunity to investigate these and save on the cost of running your applications.

In summary

CloudFront Invalidation metrics add to the transparency and rich insights already provided for Skpr customers.

We hope these metrics add significant value to your Skpr experience and increase your understanding of your application and its behaviour.

Tags

metrics
CloudFront
AWS

Getting Started

Interested in a demo?

🎉 Awesome!

Please check your inbox for a confirmation email. It might take a minute or so.

🤔 Whoops!

Something went wrong. Check that you have entered a valid email and try submitting the form again.

We'll be in touch shortly.