[exporter/datadog] Host name attributes not honoured in infrastructure list

[atmask]

Component(s)

datadog exporter

What happened?

Description

datadog exporter does not currently honour several OTEL semantics. In particular, availability_zone and host.name

Steps to Reproduce

Configure OTEL collector with the cloud._availability_zone, host.name, datadog.host.name, and datadog.host.use_as_metadata=true attributes and the hostmetrics receiver.

Expected Result

The infra list display hostmetrics under the designated hostname and AZ

Actual Result

The host name is ignored in favour of cloud vendor specific VM id (which is listed no where on the attributes when using the debug exporter for validations).

Workaround

I has to go and configure the fallback hostname on the dd exporter to get the correct node name to display. AZ is still broken

Collector version

0.96.0

Environment information

No response

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/datadog: @mx-psi @dineshg13 @liustanley @songy23 @mackjmr

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

[mx-psi]

@atmask Thanks for filing this issue. I think the information you are seeing in the infrastructure list is not the one from your OTLP resources but instead the legacy one that used to be the only sent by the Collector. To validate this and help you further, we will need more data on your configuration and payloads.

So that you don't have to share this information in public, would you mind filing a support ticket? You can link to this comment and mention me so that it gets to me. If you already have one, feel free to share the reference number instead.

I will share the resolution of the ticket here once we have dealt with it for people following from home :)

[atmask]

@mx-psi , thanks. I opened a support ticket #1603724 with more details and attached the config

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

• exporter/datadog: @mx-psi @dineshg13 @liustanley @songy23 @mackjmr

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.