Deprecate support for reading resource-related fields from span attributes

[IbraheemA]

Component(s)

connector/datadog

Describe the issue you're reporting

When transforming an OTLP span to a Datadog span (in either datadogconnector or datadogexporter), the following attributes are read from the OTLP span and used to populate the fields of the Datadog span:

• datadog.host.name,
• container.id
• k8s.pod.id
• deployment.environment.name
• service.name
• service.version

We would like these to be read from resource attributes and only resource attributes. In previous releases, some of these attributes could be set in span attributes as well - however, we are in the process of deprecating that, to match Datadog's specification. This issue is to flag this change and track the deprecation effort.

Tracking work:

We've merged a few PRs to introduce an alternative code path in the Datadog trace agent (which performs trace translation) that deprecates this functionality: see DataDog/datadog-agent#30981

This PR deprecates the functionality for when connector.datadogconnector.NativeIngest is enabled. This user who was using service.name in span attributes encountered an issue following this change..

In a future PR, we'll add a feature flag which allows users to enable the alternate code path when connector.datadogconnector.NativeIngest is disabled as well.

[github-actions]

Pinging code owners:

• connector/datadog: @mx-psi @dineshg13 @ankitpatel96 @jade-guiton-dd

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

[JaredTan95]

I think #36924 might be a related issue?

[IbraheemA]

I think #36924 might be a related issue?

That issue is concerning the datadogreceiver, which has its own translation logic separate of the one used in the exporter and connector.