[ECS] [request]: Provide Container logging details in ECS New Console UI under Task Definition
- 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**
What do you want us to build?
**Which service(s) is this request for?**
ECS UI - New Console
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
- In the ECS classic console, when we click on any task definition revision, the task definition shows container logging configurations under the container details.
In the ECS new console, there are no logging details when we observe the task definition revision info/details. We would need to look at the logging configuration in the JSON file in order to see any logging details for the container.
The ask is to add logging details under the container details in the new console UI view, without having to take extra steps and direct to the JSON file every time which is more tedious.
**Are you currently working around this issue?**
- Currently the workaround is to take extra steps to look at the JSON file configuration for the task definition to understand how logging is configured for the container, which seems tedious especially if it was readily available in the old console.
Contributor guide
Research direction
Start with the ECS New Console task definition revision view and compare its container-details presentation with the classic console and the task-definition JSON logging configuration described in the issue. Done means the new console shows the container logging details directly under container details without requiring the JSON view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100