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

[exporter/datadogexporter] Add support for custom container tags #29156

Merged

Conversation

mackjmr
Copy link
Member

@mackjmr mackjmr commented Nov 13, 2023

Description:
This PR updates github.com/DataDog/datadog-agent/pkg/trace and github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/attributes. This brings in the following PRs: DataDog/opentelemetry-mapping-go#193, DataDog/datadog-agent#20779 which add support for custom container tags (for traces, metrics and logs) via resource attributes prefixed by datadog.container.tag.*.

This PR also brings a couple other changes for traces which are reflected in the changelog:

  • Stop extracting container tags from span attributes, but only extract from resource attributes. The semantic conventions we are using to extract the container tags are meant for resource attributes, so we should only check resource attributes.
  • Stop setting the DD Format container tags as span tags, but only set these in the dedicated container tag (_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.

…-telemetry#29154

This PR updates `github.com/DataDog/datadog-agent/pkg/trace` and `github.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 by `datadog.container.tag.*`.

This PR also brings a couple other changes for traces which are reflected in the changelog:
- Stop extracting container tags from span attributes, but only extract from resource attributes. The semantic conventions we are using to extract the container tags are meant for resource attributes, so we should only check resource attributes.
- Stop setting the DD Format container tags as span tags, but only set these in the dedicated container tag (`_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.
@mackjmr mackjmr requested review from mx-psi, songy23, a team and dmitryax as code owners November 13, 2023 16:24
@mackjmr mackjmr changed the title [exporter/datadogexporter] Add support for custom container tags #29154 [exporter/datadogexporter] Add support for custom container tags Nov 14, 2023
@mackjmr
Copy link
Member Author

mackjmr commented Nov 14, 2023

The updates to the go.mod/ go.sum got brought in in these couple PRs:

So after merging main in there are no changes left other than the release notes. That said, the release notes in this PR are still relevant.

@mx-psi mx-psi merged commit f23afae into open-telemetry:main Nov 14, 2023
76 checks passed
@github-actions github-actions bot added this to the next release milestone Nov 14, 2023
RoryCrispin pushed a commit to ClickHouse/opentelemetry-collector-contrib that referenced this pull request Nov 24, 2023
…n-telemetry#29156)

**Description:**
This PR updates `github.com/DataDog/datadog-agent/pkg/trace` and
`github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/attributes`. This
brings in the following PRs:
DataDog/opentelemetry-mapping-go#193,
DataDog/datadog-agent#20779 which add support
for custom container tags (for traces, metrics and logs) via resource
attributes prefixed by `datadog.container.tag.*`.

This PR also brings a couple other changes for traces which are
reflected in the changelog:
- Stop extracting container tags from span attributes, but only extract
from resource attributes. The semantic conventions we are using to
extract the container tags are meant for resource attributes, so we
should only check resource attributes.
- Stop setting the DD Format container tags as span tags, but only set
these in the dedicated container tag (`_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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmd/configschema configschema command cmd/otelcontribcol otelcontribcol command exporter/datadog Datadog components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants