Skip to content
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

Open
h0cheung opened this issue Jul 1, 2024 · 3 comments
Open

Get container metadata in resourcedetection processor. #33821

h0cheung opened this issue Jul 1, 2024 · 3 comments
Labels

Comments

@h0cheung
Copy link
Contributor

h0cheung commented Jul 1, 2024

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 like k8sattributes 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

@h0cheung h0cheung added enhancement New feature or request needs triage New item requiring triage labels Jul 1, 2024
Copy link
Contributor

github-actions bot commented Jul 1, 2024

Pinging code owners:

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

Copy link
Contributor

github-actions bot commented Sep 2, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

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

Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants