[exporter/datadogexporter] Add support for custom container tags #29154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR updates
github.com/DataDog/datadog-agent/pkg/trace
andgithub.com/DataDog/opentelemetry-mapping-go/pkg/otlp/attributes
. This brings in the following PRs: DataDog/opentelemetry-mapping-go#193, DataDog/opentelemetry-mapping-go#174 which add support for custom container tags (for traces, metrics and logs) via resource attributes prefixed bydatadog.container.tag.*
.This PR also brings a couple other changes for traces which are reflected in the changelog:
_dd.container.tag
). We currently set the DD mapped container tags both as span tag, and in the dedicated container tag_dd.tags.container
. This should only be set in the dedicated container tag.The update to opentelemetry-mapping-go also brings in this change: DataDog/opentelemetry-mapping-go#174, which adds support for
host.cpu.*
attributes.