-
Notifications
You must be signed in to change notification settings - Fork 71
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
ECS container ID not being parsed/sent #823
Comments
Tangentially related, docker uses cgroup v2 (since docker 20.10) which does not expose the container ID in Instead, it looks like the container ID can be resolved from |
Looks like this has come up in various elastic apm repos (elastic/apm-agent-python#1691, elastic/apm#523). elastic/apm#523 (comment) is exactly the issue that we're running into. |
Proposed PR #966 |
Implemented by #966 |
@Nacoma Hi. We implemented capturing container ID in PRs #966 and #975 and it's already merged to main branch. Please try it out and let us know if it works on a AWS ECS container. Also if you could provide examples of |
That's wonderful! We have tickets in place to move to the new version. I appreciate the work you all are doing on this.
Absolutely!
|
Infrastructure correlation isn't working because the
container.id
field is not present.To Reproduce
Expected behavior
This is the ingested message received from the application/APM:
Metricbeat (elastic-agent), installed on the host, is correctly identifying the containers:
May be a different container ID now, but
/proc/self/cgroup
contains:The text was updated successfully, but these errors were encountered: