Kafka consumer is showing invalid service name in XRay Service Map

[sukrit007]

Describe the bug Service name for Kafka consumer is not leveraging service.name in OTEL_RESOURCE_ATTRIBUTES. Instead it shows name of consumer and method in XRay.

Steps to reproduce

• Use spring-boot starter application leveraging ReplyingKafkaTemplate from spring-kafka to post and consumer the message.
• Set valid service.name in OTEL_RESOURCE_ATTRIBUTES

What did you expect to see? I was expecting the name of service to match service.name in OTEL_RESOURCE_ATTRIBUTES

What did you see instead? Instead it showed me service name: " process"

Additional context

• Spring Kafka 2.7.0
• Spring Boot 2.4.2
• OTel Exporter: XRay
• OTel Collector: 0.15.1
• Environment : EKS 1.19
• Java AutoInstrumentation: 1.9

[anuraaga]

Hi @sukrit007 - thanks for reporting, this is a known issue related to messaging spans.

@willarmiros This is the issue where we don't fill service name for spans that aren't SERVER because we don't know if they are a local root or not. I have pinged https://github.com/open-telemetry/opentelemetry-specification/issues/366 to see if we can get a clearer signal there, in the mean time you may look into any other workaround we may be able to accomplish in the xray exporter.

[willarmiros]

Thanks - we will take a look at the renaming in awsxrayexporter

[sukrit007wawa]

This was the behavior with batch consumer. When we changed the consumer to Spring Cloud Stream (non-batch consumer), we are seeing spans of consumer service under producer service. Even though the two services are deployed as separate EKS Deployments with appropriate OTEL_RESOURCE_ATTRIBUTES.

Tagging @alolita

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[bryan-aguilar]

@willarmiros is this a WIP and should thus not be tagged stale?

[willarmiros]

The issue of service.name not being respected is covered here too: https://github.com/aws-observability/aws-otel-java-instrumentation/issues/158

I think we should leave this open since the change is on the collector and it's a WIP.

[bryan-aguilar]

Added it to the backlog. Should keep it from going stale until we have a better method.

[jgprogramming]

Hi @willarmiros , is there an ETA for this issue? Or any known workaround?

[willarmiros]

Hi all, thanks for raising this. I've documented the ask to prioritize service.name and we will make the change soon as long as there are no negative consequences of doing so that we can find.

[colin-humphrey]

Hey @willarmiros What's happening to this feature - it would be good to get an updated perspective, is this ready to ship or still WIP? I'll ping our TAM and Solutions Architect in parallel.

[atshaw43]

This ask would be covered by this PR. It would need some modification so that we do not promote consumer spans. https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/25176/files

[atshaw43]

This is being covered in this PR: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/29564