Grunt task to analyse and log simple metrics of static assets to Amazon CloudWatch.
This is tasks is used by the Guardian's frontend web project to monitor the performance of their client-side assets. Once the data is in CloudWatch it can then be used to set alert thresholds when certain assets get too large.
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-asset-monitor --save-dev
Location of your properties file containing your AWS api credentials. This should be a raw utf-8 text file with key=value pairs:
Level of GZip compression to use to generate compressed file size output.
Whether to convert file size output to human readable format, example:
Basic example of a Grunt config containing the monitor task.
Running monitor against multiple CSS files. All the files specified in the
src array will be analyzed by grunt-asset-monitor.
Example of using the options.
assetmonitor:dev:src:'test/*.min.css'options:gzipLevel: 4pretty: truecredentials: 'aws.properties'
Example of using a glob pattern to target many files that should be analysed by asset-monitor. The example below will analyse all the files in the
css directory that have an extension of