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 idea has been in the status of Uncommitted Candidate / Future Consideration. Whilst this idea has been in the system for quite a while, and with a relatively low level of supporting comments/votes, yet it is something which we intend to keep tracking and maintain the status as Future Consideration.
Hi Matthew, thanks for raising this RFE. We approve of the general idea of making it easier to turn tracing on in a consistent manner across widely varying functional areas of the IIB product. That said, the use case presented is an interesting justification. Typically if a user is trying to figure out where a problem lies, then they would start with user tracing to highlight whereabouts in a message flow the problem seems to be occurring. To take the use case presented, a user trace would clearly identify which of the parts 1-5 was where an exception occurred, or even where a time period where a flow thread is spending a disproportionate amount of time. Once specific resource managers get involved, or become under suspicion, typically deeper trace in a specific area might be needed such as ODBC tracing for example. Turning such more detailed specific traces on, could certainly be achieved in a more consistent manner. Let's use this RFE to track a consistent method of turning on tracing for the areas listed. You mention that you'd like other traces to be exposed, but concede that your list covers many traces which are already available. If there are specific areas where you feel more tracing should be externalized, perhaps you could raise that as a separate RFE for clarity of tracking please.
Regarding Damien Collis's comment, I think this is actually a slightly different request. Tracing of the type and depth mentioned in the original RFE is very much an exceptional situation rather than something intended for production usage. For general auditing / logging I think Damien would be better served by taking a look at either Flow Activity Log or the Resource Statistics options which are already available with the product.
Status of the RFE is updated to Uncommitted Candidate.
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
Within our environment this would be used for auditing/logging functionality within the production environment, rather than debug/tracing. It would be good if there was some control over the trace file generation that would allow for rolling files based on filesize and/or date so that old files could be archived without stopping and starting processes or issuing commands to clear the trace logs. Functionality similar to log4j RollingFileAppender and/or DailyRollingFileAppender
Within our environment this would be used for auditing/logging functionality within the production environment, rather than debug/tracing. It would be good if there was some control over the trace file generation that would allow for rolling files based on filesize and/or date so that old files could be archived without stopping and starting processes or issuing commands to clear the trace logs. Functionality similar to log4j RollingFileAppender and/or DailyRollingFileAppender