Containers-roadmap: [ECR] CloudWatch metrics for API usage

Created on 10 Jul 2019  路  7Comments  路  Source: aws/containers-roadmap

ECR should publish CloudWatch metrics that show the call count per API.

We're interested in feedback about these are the right metrics and how valuable these would be to customers.

ECR Proposed

Most helpful comment

Additionally Id like to see metrics on the last pull for an image. It would make it easier to see what images are truly being used

All 7 comments

Furthermore I think metrics to identify how close you are to having to request service limit increases would be very useful to make it easier to be proactive.

Additionally Id like to see metrics on the last pull for an image. It would make it easier to see what images are truly being used

Furthermore I think metrics to identify how close you are to having to request service limit increases would be very useful to make it easier to be proactive.
@jespersoderlund Thanks for the feedback.

Additionally Id like to see metrics on the last pull for an image. It would make it easier to see what images are truly being used

@sstkwayne I see why that data is useful. It'd be great to know how you'd plan to consume it. Here are some ideas we've heard in the past:

  1. View the data via ECR's list/describe APIs, such as https://docs.aws.amazon.com/cli/latest/reference/ecr/describe-images.html
  2. Use the data to clean up old images via a lifecycle policy rule.
  3. Regardless of the last pull time, link from the image in ECR to where the corresponding container is running in ECS or EKS.

Additionally Id like to see metrics on the last pull for an image. It would make it easier to see what images are truly being used

@sstkwayne I see why that data is useful. It'd be great to know how you'd plan to consume it. Here are some ideas we've heard in the past:

  1. View the data via ECR's list/describe APIs, such as https://docs.aws.amazon.com/cli/latest/reference/ecr/describe-images.html
  2. Use the data to clean up old images via a lifecycle policy rule.
  3. Regardless of the last pull time, link from the image in ECR to where the corresponding container is running in ECS or EKS.

@jtoberon I would like to use it to clean up old images and see where it is being used. We have some applications which are pretty stable and aren鈥檛 getting many updates so an age based lifecycle rule wouldn鈥檛 be good for us as we might inadvertently delete the image.

You can now monitor ECR API usage using CW metrics, and see how it relates to your per-account Service Quotas (rate limits). This is live in preview, we'll announce shortly. Read more: https://docs.aws.amazon.com/AmazonECR/latest/userguide/monitoring-usage.html

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tabern picture tabern  路  3Comments

adlemich picture adlemich  路  3Comments

pauldougan picture pauldougan  路  3Comments

sarath9985 picture sarath9985  路  3Comments

clareliguori picture clareliguori  路  3Comments