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.
Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. Unfortunately on this occasion we do not intend to take this idea further forward. There are several alternative mechanisms available to meet the use-case presented. Since creation of the suggestion, the subscription topic has been enhanced to incorporate the "applicationName" which helps narrow in to a smaller set of publications:
topicRoot/integrationNodeName/Monitoring/integrationServerName/applicationName/messageFlowNameIt is also possible to only emit events from a flow when the propagation goes down a particular terminal on a message flow node (eg a catch or a fail terminal would have much lower volume of messages than a standard out terminal for example). You can also apply XPath expressions to cause monitoring events to only be emitted for certain messages going through a particular flow node and not others (ie dependent on some aspect of message payload, choose to emit the event or not). Lastly, it is also possible to use content based filtering of the publications to avoid "data overload" in your subscriber. Given that this RFE has been open since 2012, and with limited supporting votes cast, we suspect the importance of this issue is long since out of date in any case. Idea is closed.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
Thanks for raising this requirement. Event monitoring is an important focus area for us. If you look at every release since the original implementation in V6.1.0.2 you'll see that we've been continually improving the technology, whether it's the transactional behaviour in V7, or the record and replay enhancements in V8. So as the events get used more and more, the requirement you raise is going to be increasingly important. We'll investigate this requirement in a follow-on release.