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

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.

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.