Monitor the Server by Ignoring the Queue Name

In JMS example, the application is making calls to a message server that handles several queues. The sample destination names look like this:

• AccountQ
• AccountReplyQ
• AccountRecQ
• AccountDebitQ

The default automatic discovery rule detects one backend for each unique destination and so the flow map shows one queue backend for each different queue name. In this example, each of the above would show as a separate backend on the application flow map. If you are interested in monitoring the performance of the server and not each queue name, you can modify the configuration to ignore the Destination property and use just the Type and Vendor.

To achieve this result, you create a new custom JMS Discovery Rule.

Taking IBM MQ for another example, the application is making calls to a message server that handles several queues. The sample destination names look like this:

• MQhostwest-US:1521
• MQhosteast-US:1521
• MQhostsouth-US:1521

The default automatic discovery rule detects one backend for each unique destination and so the flow map shows one queue backend for each different queue name. In this example, each of the above would show as a separate backend on the application flow map. If you are interested in monitoring the performance of the server and not each queue name, you can create a discovery rule that just uses the Host and Port, as follows: