APM MQ Monitor 23.3 unexpected changes (New regexp format to filter queues AND New queues by types structure for metrics)

Products

• DX Application Performance Management

Issue/Introduction

After upgrade MQ Monitor from 20.3 to 23.3, we have noticed 2 issues:

ISSUE #1 - queue filtering (regexp) is not working as expected:

Previous property and value used:

    introscope.agent.mq.monitor.profiles.N1IUBK01.queue.filter.includeonly.regex=^(?\!SYSTEM).*$|(?=SYSTEM\.JMS\.D\.[A-Z][A-Z][A-Z]\.).*$

New property and value used:

    introscope.agent.mq.monitor.profiles.N1IUBK01.includeQueueRegexFilter=^(?\!SYSTEM).*$|(?=SYSTEM\.JMS\.D\.[A-Z][A-Z][A-Z]\.).*$

The result is that we can still see all the SYSTEM.* queues

ISSUE #2 - Metric View shows the queues by type i.e. Local, Alias, Transmission etc, whereas previous agent had all Local, Alias, Model queues under ‘Queues’. 

This is a major issue as we will need to amend all our existing alerts to include the queue type in the metric grouping.

Environment

APM MQ Monitor 23.3

Resolution

The problem is related to defect DE561941 to be fixed in next release. 

Below new properties have been introduced:

• • We have introduced 3 new properties which you need to update before restart:
    • agent.mq.monitor.keepLegacyQueueMetricPath = true
      • Keep it true in order to see Old Queue metric structure.
      • No need to update JSON in this case.
    • agent.mq.monitor.profiles.default.includeQueueRegexFilter.onResponse =^(?!SYSTEM).*$|(?=SYSTEM.ADMIN.[A-Z][A-Z][A-Z]\\.).*$
      • This is new property introduced to allow Queue filter with regular regex.
      • The regex in above example is same which you provided.
    • agent.mq.monitor.profiles.default.includeChannelRegexFilter.onResponse =
      • Additionally we also provided a property for Channel filter.
      • You need to update it only if you want some filter on Channel as well.

Additional Information

Configure IBM WebSphere MQ Infrastructure Extension in Bundle.Properties File