APM agent with RabbitMq listener

Kibana version: 7.9.1

Elasticsearch version: 7.9.1

APM Server version: 7.9.1

APM Agent language and version: Java agent 1.18.1

Browser version: Chrome 79.0.3945.130

Original install method (e.g. download page, yum, deb, from source, etc.) and version: From elastic on Windows

Fresh install or upgraded from other version?: Fresh Install

Is there anything special in your setup? We have integrated a Spring boot applications which has both rest endpoints for certain set of transactions and RabbitMQ where our core business interest is.

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant): Rest based transactions are being captured by APM as transactions and errors. we can see lot of indices being created. However we have issue with capturing transactions based out of rabbitMQ listeners, we suspect the event associated to rabbitMQ are not being triggered to APM. While we understand RabbitMQ is not supported by the APM yet, is there a reason by transactions are not being captured post the listener event on the application.

**Steps to reproduce: **:

  1. Setup a service with Rabbit MQ listener.
  2. Post messages to Queue.
  3. Login to Kibana > APM, notice that transactions are not being triggered and there is no option to load/change filters.

Errors in browser console (if relevant): No Errors. Transactions don't get listed on the APM dashboard. Jave metrics and other HTTP metrics get loaded.

Provide logs and/or server output (if relevant): Will provide if required.

Hi @nagabhushan.tr, we have an open PR that adds support for RabbitMQ, and it's quite close to being merged and included in the next release.

In order to test it, you can use this snapshot.

Have a nice day!

Thank you @Sylvain_Juge, Let me give a try and respond back.

@Sylvain_Juge, I attempted to use the snapshot jar that you provided, it is able to capture the rabbitMQ message however i noticed the following.

  1. Agent doesn't keep track of the transactions and interactions with downstream microservices or database.

  2. Transaction is not plotted on the service map.