Skip to main content

MQ Monitoring – Automatic Discovery of New Queues in Queue Manager

  • July 6, 2026
  • 1 reply
  • 19 views

SUNNY CHINNARAPU

Hello Community,

We have a requirement to automatically discover newly created queues within an already monitored IBM MQ Queue Manager.

Currently, when a new queue is created, the queue name must be manually added to the discovery snippet before SL1 can discover and monitor it. In environments where queues are created frequently, this creates additional operational overhead and increases the risk of queues not being monitored until manual intervention occurs.

Requested Enhancement

  • Automatically discover newly created queues under monitored Queue Managers.
  • Detect new queues during scheduled discovery/re-discovery cycles.
  • Automatically create queue components and apply existing monitoring policies.
  • Support include/exclude patterns to control which queues are monitored.
  • Eliminate the need to update discovery snippets whenever queues are added.

Use Case

Our MQ environment is dynamic, and new application queues are introduced regularly. Having to manually maintain queue names in the discovery configuration is time-consuming and difficult to scale.

Benefits

  • Reduced manual administration.
  • Faster onboarding of new MQ queues.
  • Improved monitoring coverage.
  • Reduced risk of unmonitored production queues.

Is anyone else looking for similar functionality? It would be great to have this capability natively supported in a future IBM MQ PowerPack release.

1 reply

Forum|alt.badge.img
  • Community Manager
  • July 9, 2026

Hey ​@SUNNY CHINNARAPU  
We should look to have this in IdeasHub section (and not the discussion section).

The design around having the user define what queue managers to discovery has been a difficult question to answer out of the box and hence since the initial version, we have let the user define what they want to discover. The rational has been that if you have 100s of queue managers, you might not want to monitor most of them. 

The explicit definition of what to discover was in the snippet (and not the cred) because of reasons that are not relevant, but that is the best approach that we could design. 
If it is too much of a moving target for you to keep the snippet updated with new queue managers, we might not have a good answer for the approach you can take. We are not looking at providing “*” where everything is being discovered. 

 

Happy to talk over things. Please send me an email and I will reach out to you. 

 

Dipak