Skip to content

Add support for ECS API in awsecscontainermetrics receiver #40481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mw-advait opened this issue Jun 4, 2025 · 1 comment
Open

Add support for ECS API in awsecscontainermetrics receiver #40481

mw-advait opened this issue Jun 4, 2025 · 1 comment

Comments

@mw-advait
Copy link

Component(s)

receiver/awsecscontainermetrics

Describe the issue you're reporting

So I was trying to use awsecscontainermetrics receiver and found out that it supports limited amount of metrics and there is more info available in AWS ECS container insights.
So I am thinking about a way that we can add support for ECS API within awsecscontainermetrics receiver which will contain more extended custom metrics which might be helpful for other users.
I am thinking about running a sidecar container approach.
However, let me know if any other way is possible or any guidance regarding the implementation details.
Thanks!!

Also, let me know if i can work on this ECS API integration.

@mw-advait mw-advait added the needs triage New item requiring triage label Jun 4, 2025
Copy link
Contributor

github-actions bot commented Jun 4, 2025

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@ChrsMark ChrsMark added waiting-for-code-owners and removed needs triage New item requiring triage labels Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants