Service Bus - Apache Camel AMQP: consumers are not being reported in application map

[apoguy]

Expected behavior

We are running an app using Apache Camel with amqp component, connected to Service Bus queues and topics. When sending messages we can see the traces and it is displayed on application map just fine:

However, received messages even tho they appear in traces and end-to-end transactions:

they are not displayed in application map. I believe this is an issue with the agent, as we have other java apps that do not use Camel AMQP that are being reported just fine. It could be a Camel AMQP issue, however, as in traces the "recieves" show up, suggests that is more an application insights issue.

To Reproduce

This can be reproduced using a basic apache camel routes:

<route id="test">
   <from uri="direct:test"/>
   <!-- set any header for topic filter -->
   <to uri="amqp:topic:stx_healthcheck_topic?disableReplyTo=true"/>
   <pollEnrich timeout="2000">
      <constant>amqp:topic:stx_healthcheck_topic/subscriptions/{{subName}}</constant>
   </pollEnrich>
</route>

System information

Please provide the following information:

• SDK Version: 3.1.1
• OS type and version: RHEL ubi image
• Additional relevant libraries (with version, if applicable): Apache Camel AMQP 2.24.0

[apoguy]

Noticed there is a BETA version, tested BETA 4, with even less success, now receives don't even show up in logs or traces:

[phanbyte]

Noticed there is a BETA version, tested BETA 4, with even less success, now receives don't even show up in logs or traces:

i have the same issue, no solution found yet. waiting for support.

[trask]

@apoguy we pulled in Apache Camel as preview instrumentation in the latest release:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config#preview-instrumentations

[apoguy]

@trask yeah, noticed Yesterday and I already implemented it and works like a charm!

Thanks for that!

I opened another issue for Akka actors and Akka HTTP instrumentation. Mostly because now all telemetry from Akka actors is being tracked as a single transaction, so correlation keeps loading events endlessly.