aws / aws/containers-roadmap

[Fargate] [request]: cloudwatch metric or container stats for open connections (e.g. "conntrack")

Open
#995 0 comments 10 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

It would be great if we could get some "conntrack" metrics for ECS/Fargate, either via cloudwatch metrics (containerinsights) or via the container-stats metadata endpoint (which could then be processed by another agent, such as datadog).

In our use case, especially having insights into "open connections" it would allow us to track if applications are leaking connections (could also be interesting for file descriptors?), and/or setting up alarms, especially if there are certain limits on those.

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or implementation entry points are named. Start by determining whether ECS/Fargate should expose conntrack and file-descriptor data through CloudWatch Container Insights or the container-stats metadata endpoint. Done would require an agreed metric surface and a documented implementation path.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.