Additional Docker Container Metadata to [resourcedetection/docker]

[amal-v]

Component(s)

processor/resourcedetection, processor/resourcedetection/internal/docker

Is your feature request related to a problem? Please describe.

We are running the OTel collector to gather logs from a docker containers on a docker host. The docker resource detection processor only gives you the following.

Name	Description	Values	Enabled
host.name	The host.name	Any Str	true
os.type	The os.type	Any Str	true

based on this document. We need additional container metadata to segregate logs.

Describe the solution you'd like

The resource detection processor adds:

• Container ID
• Name
• Image
• Labels

Similar to what's implemented in Filebeat.

Describe alternatives you've considered

Alternate would be a dockerattributesprocessor like k8sattributesprocessor to enrich the logs with additional metadata.

Additional context

No response

[github-actions]

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

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

[ChrsMark]

I think this request is quite valid. From what I can understand the docker resource detector so far aims on host related attributes so not sure if container related metadata would fit there. I would lean towards creating a standalone dockerattributesprocessor component as it was suggested.

Pinging @mx-psi as the original author of the docker detector.

[mx-psi]

The resource detection processor adds:

• Container ID
• Name
• Image
• Labels

What container ID would we be fetching here? The Collector one? The purpose of the resourcedetection processor, as I understand it, is to populate the resource from the environment that the Collector is running on. If these attributes are about the Collector, then it would make sense to add them, but if they refer to other containers, then I don't think it makes much sense

[ChrsMark]

I would assume these would refer to other containers. At least that's what Filebeat, that was mentioned, does.

[github-actions]

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:

• processor/resourcedetection: @Aneurysm9 @dashpole

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

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.