Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Why can't I see my ActiveMQ server in the transaction flow?

Dynatrace Advisor
Dynatrace Advisor


Hi Markus,

I believe you have to change JMS sensor configuration from agent group to be "active and start PurePaths" .

i hope this help you .



Hi Abdel - thank you for your comment. This is a FAQ entry that contains question and answer already. See the answer to this question below. I initially had the answer in the wrong place and have now corrected that.

Dynatrace Advisor
Dynatrace Advisor

It is a common misunderstanding to instrument an ActiveMQ server to get
extra visibility into JMS nodes.

Dynatrace instruments the JMS client API
(send/receive/onMessage) which is sufficient to get visibility into JMS.
Instrumentation of an ActiveMQ server is not needed and optional. Even when an
agent is injected, the ActiveMQ server will not show up as a separate node for
JMS communication.

You said "Instrumentation of an ActiveMQ server is optional", do you know to opt for it? In our product there're occasionally big delay between client sending JMS message and server receiving it. I added a few ActiveMQ server methods in sensor rules, hoping to understand what's happening inside ActiveMQ, but I still cannot see them stitched to purepaths.