Skip to Main Content

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace App Connect
Created by Guest
Created on Apr 7, 2023

APP Connect Enterprise-Stop emitting or disabling monitoring events based on user inputs like payload size or log level at broker/eg level using mqsi change commands

All the ACE(App Connect Enterprise) applications use a built-in feature (called event monitoring) of IBM ACE, for emitting monitoring events to capture the payloads as part of their business transactions. All these monitoring events are emitted from topic “$SYS/Broker/{BRK_NAME}/Monitoring/{EGName}/# “ and get pushed to input MQ via MQ Subscriptions through Pub-Sub pattern.

Ask here: To stop emitting or disable monitoring events based on user inputs like payload size, or log level at broker/eg level by executing any mqsi change command

We are looking for this new Feature which should be supported by ACE version 12.0.4 or higher

Idea priority High
  • Admin
    Ben Thompson
    May 24, 2023

    Idea review. Thank you for taking the time to raise this suggestion, and thank you to the many CVS/Aetna affiliated voters who have recently registered their interest in this request. As noted, ACE applications provide a built-in feature which uses MQ Publications to be emitted as monitoring events when data passes through particular message flow nodes, and particular terminals of those nodes ... which can be configured statically both when the flow is created, and also overridden using a monitoring profile in a specific environment. The product in its current form also allows granular capability to turn monitoring on and off for particular deployed flows or for deployments to whole integration servers. There is also the ability to influence how much data is injected into each monitoring event - XPath expressions can be used to pick out specific fields from the main payload of data travelling through a message flow rather than including the whole payload ... This is a common technique for avoiding monitoring messages becoming too large. Using Event Filters, ACE also lets the publication of a monitoring message be dynamically controlled based on the presence of a particular value in the tree ... We appreciate that event emitting based on payload value is slightly different to payload size (that is, unless there is something in the tree which informs us of the payload size such as from a FileInput node for example). If we were to go ahead with the request, it sounds like the better option might be to not "only emit the event based on payload size" but instead still emit the event but truncate it should it breach a size threshold ? Just a thought, which you and others from the community may care to comment on. Status updated to Future Consideration.

    1 reply
  • Guest
    Apr 17, 2023

    This is a high priority item for us as there are events being emitted that cannot be controlled through the flows from a size perspective. This is causing messages being sent to dead letter queues and is impacting MQ stability in production.