[CAMEL-15230] RabbitMqSpanDecorator - Invalid Parent Span Id when EXCHANGE_NAME header not set

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.3, 3.5.0
• Component/s: camel-opentracing
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Matt Robbins
• Created: 23/Jun/20 10:19
• Updated: 29/Jul/20 14:37
• Resolved: 29/Jul/20 14:34

Description

It seems like there is no strict requirement for rabbitmq.EXCHANGE_NAME header to set by a producer e.g. the following code "works":

from("direct:foo")
   .to("bar.exchange?queue=bar.queue&autoDelete=false")
   .end()

However in this instance a span will be created with null as the operation name.

Such spans will be ignored by the collector e.g. Jaeger, which results in subsequent spans having missing parents and "invalid parent span id" warnings appearing.

Doing the following prevents this.

from("direct:foo") 
  .setHeader("rabbitmq.EXCHANGE_NAME").simple("bar.exchange")
  .to("bar.exchange?queue=bar.queue&autoDelete=false")
  .end()

It seems like we don't necessarily need the overridden getDestination method in the RabbitMqSpanDecorator and could fall through to the base implementation?

Happy to raise a PR but thought I would collect thoughts in case I had missed some subtlety. 

 

 

 

 

 

Issue Links

• links to: GitHub Pull Request #3958