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!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI! Discover how Splunk’s agentic AI ...

[Puzzles] Solve, Learn, Repeat: Dereferencing XML to Fixed-length events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Stay Connected: Your Guide to December Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...