-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Get container metadata in resourcedetection processor. #33821
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
processor/resourcedetection, processor/resourcedetection/internal/docker
Is your feature request related to a problem? Please describe.
There is a docker detector, but it only generates host metadata.
In components such as javaagent, there are resource providers that can get the
container.id
field and associate it with container metadata. Is it possible to add similar functionality to this component?Describe the solution you'd like
Add detector to get
contianer.id
If a container runtime API is mounted, e.g.docker.sock
, associate the information directly. Otherwise we can provide another component likek8sattributes processor
that runs on the host and forwards the data and adds container metadata.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: