Cloud Management and AIOps
Hide about this portal
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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.
I see this idea has been opened against the Instana team as opposed to the ACE team, but commenting here from the ACE product development perspective ... ACE subflows are a useful mechanism in the tooling to define a set of message flow nodes as a reusable unit across multiple flows. A subflow can be defined in a static library or in a shared library depending on whether you would like updates to the subflow to be individually applied to a single embedding parent flow (static) or multiple embedding parent flows (shared) … but at runtime the executing message flow thread from the parent flow continues to execute the logic in the subflow … so essentially this is a tooling concept as opposed to a runtime concept... This means that if you switched on the ACE Open Telemetry feature, it would influence HTTP and MQ transport nodes regardless of whether they occur in the parent flow or in the subflow. If you would like to see more granularity with traces offered for other transports, or "internal" nodes such as Compute, JavaCompute, Mapping node etc. then this could be done … but it would be good to know which specific nodes would be your priority.