[ECS] [request]: More granular status for Pending tasks
- 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**
More granular status around ECS task activities while in the pending state would be helpful to quickly diagnose potential problems. For example, beginning image download, ending image download.
**Which service(s) is this request for?**
ECS Fargate and likely EC2-based ECS.
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently, it is difficult to diagnose why a task might be stuck in pending, and this can impede time-sensitive investigations into production failures. Presently, the Events log and the UI only shows "Pending" and provides little to no information on what is going on underneath the hood.
**Are you currently working around this issue?**
The only workaround we have is to wait for the Pending task to fail (which can be > hour) and then see what the failure is.
**Additional context**
There are a variety of potential solutions that could help. It could be added ECS events (though, this could flood the event log UI if there is no way to filter these). It could be a change to the UI for a task to show what it is currently engaged in doing (potentially avoiding the ECS event log entirely).
Contributor guide
Research direction
No files, tests, or implementation entry points are identified in this roadmap request. Start by reviewing how ECS Fargate and EC2-based ECS expose pending-task events and status, then define a concrete status or event surface; done would provide actionable visibility into stages such as image download.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100