Integration
This is an IBM Automation portal for Integration 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 updates on 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.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
In MQ 9.2 (and IT29783 for MQ 9.1) we made significant performance improvements to how the queue manager status can be queried using 'show qm-status' and its equivalents in REST and SNMP.
As previously suggested, it is also possible to configure a log target to generate SNMP traps whenever we output an AMQ log message to report the HA or DR status has changed. The log target broadcasts an SNMP notification (trap) when the event occurs, so the SNMP server listens on a port for notifications instead of actively polling status that might timeout. If there is a problem specifically with the Tivoli monitor not reporting these alerts in time, then that would have to be taken up through that product's service or enhancement processes.
We have no current plans to make any additional changes in this area.
The problem is that if Tivoli subscribes to the System Log to receive the HA status, it receives a timeout because the query takes more than 10 seconds to give a response and therefore cannot be activated.
The option to subscribe to an event log to generate the alert requires configuration and for a more agile monitoring we believe that the best option would be to activate the error code in the SNMP traps like any other event.
Activating this functionality would be more agile and without additional configurations.
The MQ Appliance 9.2 firmware records messages in the MQ system log when the HA or DR status changes. The HA status notifications are documented in Knowledge Center at https://www.ibm.com/support/knowledgecenter/SS5K6E_9.2.0/com.ibm.mqa.doc/monitoring/mo00075_.htm. A similar topic exists for the DR notifications. You can configure a log target to subscribe to these log events and send them as an SNMP trap. An example of how to create a log target that generates SNMP traps is documented at https://www.ibm.com/support/knowledgecenter/SS5K6E_9.2.0/com.ibm.mqa.doc/configuring/co00645_.htm, which you can adjust to subscribe to the MQ HA events you require. Does this capability satisfy your requirement?