[ECS] [request]: Metrics for fargate containers using service discovery

[ghoshrahul]

Community Note

• Please vote on this issue by adding a 👍 reaction 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 Metrics for Fargate containers which use service discovery and not load balancer

Which service(s) is this request for? This could be Fargate, ECS, EKS.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? When any container is attached to the load balancer(internal/internet), we get metrics such as total request count, number of 4xx and 5xx, average latency etc. We would like the same metrics to be available for the fargate containers using service discovery instead of load balancer.

Are you currently working around this issue? No workarounds so far

Additional context The containers could be public or private.

[ollypom]

Hi @ghoshrahul , thank you for creating an issue. In 2022 AWS announced ECS Service Connect, which builds on ECS Service Discovery. If you leverage ECS Service Connect, it exposes Request Counts and Counts by Response Code in Cloudwatch and the ECS Console.