This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
IBM Turbonomic ARM
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
MQ Monitoring: Monitor the same Qmgr name on different hosts in one agent configuration.yaml
Monitor the same name Qmgr on different hosts in one agent configuration.yaml is not supported for MQ sensor. MQ sensor can monitor the same name Qmgr on different hosts, but need to be monitored from different agent host.
MQ sensor support RDQM Qmgrs by 2 solutions:
- Monitoring the same name Qmgr on each RDQM host by local monitoring, that is, don't set host and IP in MQ configurations on 2 or 3 hosts, and Qmgr will be displayed interface part in each host as local monitoring way. Thus Qmgr with physical IP/physical host name will be displayed, as QmgrName@IP. By this way, when this Qmgr is in active status, Qmgr metrics data will be displayed; when it is not active, no data will be shown. And the data for each Qmgr is for when it is in active status.
- Monitoring the same name Qmgrs with floating IP, that is , to set host and IP for MQ sensor in agent configuration.yaml, and by this way, Qmgr will be displayed as a separated box as QmgrName@IP in infrastructure view by remote monitoring way. And Qmgr will display data when it is in active status, no matter which host the Qmgr is active on. By this mode, all historical data is on one Qmgr, but it can't show which host the active qmgr is running on.
The enhancement would be for the sensor to handle multiple queuemanager and broker with same name. The business reason is because the team might not know/look for local hosted solution on the prod server and broker and associated queue manager will be sitting behind load balancer can have the same name on different servers.
A suggested approach would be to use hostname + brokername together wherever possible to distinguish.
Do not place IBM confidential, company confidential, or personal information into any field.