Library instrumentation stays as Datadog in operation name (or Primary Operation).

[nicoroms]

Component(s)

exporter/datadog, receiver/datadog

What happened?

Description

Traces receiver comes with InstrumentationScope Datadog 4.20.0 causing that datadog exporter create traces with Datadog instead of original library (like express, http, netty, etc). This change causes that backend recognize as original operation name.

And this happen in datadog traces view:

Metrics created in datadog are called with Datadog.server too

** span_name_as_resource_name on the exporter side seems to fix this behaviour on the traces, but metrics generated (like trace.express.request.hits) stay with the name trace.Datadog.server.hits, which is wrong.

Steps to Reproduce

Instrument app with datadog sdk and otlp collector with datadog receiver, any export to datadog will cause this

Expected Result

Instrumentation Scope should be the same as origin and not one created by datadog receiver or a config to keep the same behaviour of traces.span_name_as_resource_name in metrics.

Actual Result

Collector version

0.93.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

receivers:
  datadog:
    endpoint: ${POD_IP}:8126
    read_timeout: 60s
exporters:
  datadog:
    traces:
#      span_name_as_resource_name: true
    api:
      key: 

processors:
  batch:
    send_batch_max_size: 1000
    send_batch_size: 100
    timeout: 10s


extensions:
  health_check:

service:
  extensions: [health_check]
  pipelines:
    traces:
      receivers: [datadog]
      processors: [ batch]
      exporters: [datadog]

Log output

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/datadog: @mx-psi @dineshg13 @liustanley @songy23 @mackjmr
• receiver/datadog: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy

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

[mx-psi]

Thanks for filing this @nicoroms. This is probably related to #1909 but I will keep this open until we verify this.

[mx-psi]

I am going to close this as a duplicate of #1909 indeed. This

** span_name_as_resource_name on the exporter side seems to fix this behaviour on the traces, but metrics generated (like trace.express.request.hits) stay with the name trace.Datadog.server.hits, which is wrong.

is not mentioned already on the original issue so I will highlight it in our internal tracking for this issue, but otherwise this is a particular manifestation of the general issue on #1909