aws / aws/containers-roadmap

[Fargate] [Metrics]: Container Insights Duration Metric

Open
#635 2 comments 3 reactions 0 assignees View on GitHub
Fargate Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
It would be great to be able to have metrics to know how long a task runs for. Currently, for Lambda there is a `Duration` metric.

**Which service(s) is this request for?**
Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Knowing how long a task typically takes can be used as a benchmark for code improvements. This ensures the changes are moving in the right direction.

**Are you currently working around this issue?**
We're logging the total duration to CloudWatch Logs then pulling it out of the logs manually.

Contributor guide

Open the contributing guide

Research direction

Review the Fargate and Container Insights service documentation first, since the issue names no repository files, tests, or implementation entry points. Confirm the requested task-duration metric's scope and acceptance criteria with maintainers; done would mean the metric is defined and available for Fargate tasks.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.