Closed twrichards closed 8 months ago
Now that the reaper is back in action (see https://github.com/guardian/grid/pull/4145) we can no longer rely on the total count in ES for the alarms which hang-off the metrics produced by image-counter-lambda (see https://github.com/guardian/editorial-tools-platform/blob/main/cloudformation/media-service-account/image-counter-lambda.yaml). These alarms exist for two reasons...
image-counter-lambda
This PR facilitates a new alarm to capture reason 1.
2 is much harder since we're reaping at a variable rate (effectively based on the ingestion rate from the moment 20 days prior).
Seen on auth, usage, image-loader, metadata-editor, thrall, leases, cropper, collections, media-api, kahuna (merged by @twrichards 9 minutes and 57 seconds ago) Please check your changes!
Now that the reaper is back in action (see https://github.com/guardian/grid/pull/4145) we can no longer rely on the total count in ES for the alarms which hang-off the metrics produced by
image-counter-lambda
(see https://github.com/guardian/editorial-tools-platform/blob/main/cloudformation/media-service-account/image-counter-lambda.yaml). These alarms exist for two reasons...This PR facilitates a new alarm to capture reason 1.
2 is much harder since we're reaping at a variable rate (effectively based on the ingestion rate from the moment 20 days prior).