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.
thanks for considering the idea
Thank you for raising this idea. We are keen to continue improving our support for OpenTelemetry Tracing, and we can see the value in allowing support to extend to richer information being carried in the OTEL header. In the case of custom data which goes beyond the OTEL specification, we are keen that such a feature should not be abused by users wanting to carry payload information into their OTEL monitoring tools … The danger in these circumstances is that the OTEL messages could become so large that performance of the solution becomes untenable. In this case the suggested property appears to be intended to show the kind of ACE environment from which the OTEL message was generated (eg Test versus Dev versus Prod etc) which would typically only be a few characters long, but the implementation would likely need to restrict the allowable length of the data in order to ensure this was not abused for other purposes. Status of the idea is updated to Future Consideration.