[processor/resourcedetection] Additional docker attributes

[schewara]

Component(s)

processor/resourcedetection

Describe the issue you're reporting

It would be super helpful if the Docker Metadata would support more attributes, like the ones proposed in https://opentelemetry.io/docs/specs/semconv/resource/container/

An example use case would be a CI/CD Pipeline where multiple integration tests are running in parallel for different feature branches, which can only be distinguished by a unique container.name or container.image.tag

[github-actions]

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

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

[crobert-1]

I think this is a good idea. Here's the current list of resource attributes we're getting from Docker.

This will require some level of plumbing of these resource attributes. The resource detection processor is getting docker data from internal/metadataproviders/docker (ref), which is getting data from Docker's golang client package. For any new container resource attribute we'll have to add it to the internal metadata provider, and then get it from there. (This also means we're blocked by the Docker client if data we want isn't exposed.)

@schewara would you be interested in adding these resource attributes?

[schewara]

@crobert-1 Generally I would be interested, but therefore I need to learn Go first, which might take a while until I get around it.

[crobert-1]

@crobert-1 Generally I would be interested, but therefore I need to learn Go first, which might take a while until I get around it.

Fair point 🙂

[hq-conf]

Has there been any work on pulling additional docker attributes, either as part of resourcedetection or dockerstats? Specifically, I am looking for the container.image.tag - as it stands, am I correct in saying that I would need to write a transform to extract this as a custom attribute?

[crobert-1]

@hq-conf You might want to try the k8s attributes processor, it looks like it can get thecontainer.image.tag.

[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.

[schewara]

How would the actual configuration for the k8s attribute processor look like to grab the labels from a docker container?

[crobert-1]

How would the actual configuration for the k8s attribute processor look like to grab the labels from a docker container?

The README has information for how to accomplish this. There's also a config example that shows how to extract metadata from the k8s environmnent.

[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.