AppD Archive

Custom JMS rule: Snapshot call graph indicates wrong JMS destination as BT entry point

CommunityUser
Splunk Employee
Splunk Employee

Hi,

we are running a java agent version 3.9.8.7 GA against a controller version 3.9.8.0 (build 20). We have configured several custom JMS rules for Business Transaction Discovery. These custom Rules use a regex to match certain queue names (JMS Message Destination). To match traffic on the queue "QL00.MT3Z.TEC" were using for example the regex "(QL.{2}\.M.{1,2}Z\.TEC$)|(QR.{2}\.A.{1,2}D\.TEC$)".

image.jpeg

When we now look into a snapshot for the BT "TEC" discovered by this custom rule the snaphot indicates a wrong queue as BT entry point inside the call graph:

image.png

Looking at the server and agent logs (debug-mode) we definitely see, that the TEC queue was used and not the FPM queue as shown in the snapshot call graph. Note: There's a custom rule for the FPM case, too ( Regex "(QL.{2}\.M.{1,2}Z\.FPM$)|(QR.{2}\.A.{1,2}D\.FPM$)").

Can anybody explain this behaviour? Is this a bug in the gui used to render BT snaphots?

Regards,
Thorsten

0 Karma
Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...