With connect.datadogconnector.NativeIngest enabled, during APM stats metric aggregation, only the resource attributeservice.name would be used for service name, while the span attributeservice.name attribute would be ignored.
This is believed to be a bug because, in Datadog backend, the service value in the span is still using span attributeservice.name, while the service value in APM metrics uses the resource attributeservice.name.
For these kind of spans, the APM metrics related UX would be broken because of the inconsistencies.
Steps to Reproduce
Send a span with attribute service.name value sname and resource attribute service.name value rname
For example,
Component(s)
connector/datadog
What happened?
Description
With
connect.datadogconnector.NativeIngest
enabled, during APM stats metric aggregation, only the resource attributeservice.name
would be used for service name, while the span attributeservice.name
attribute would be ignored.This is believed to be a bug because, in Datadog backend, the
service
value in the span is still using span attributeservice.name
, while theservice
value in APM metrics uses the resource attributeservice.name
.For these kind of spans, the APM metrics related UX would be broken because of the inconsistencies.
Steps to Reproduce
Send a span with attribute
service.name
valuesname
and resource attributeservice.name
valuername
For example,Expected Result
APM metrics with attr
service:sname
.Actual Result
APM metrics with attr
service:rname
.Collector version
v0.110.0
Environment information
Environment
OS: macOS Sonoma 14.6.1, arm64
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response