IBM Z Software
This portal is to open public enhancement requests against IBM Z Software 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.
Thank you for this RFE, your votes and feedback.
From the comments and engagement we've had around this RFE, the need here seems to be to improve the usability around:
- Gathering specific trace for a specific API in production (for IBM support)
- Diagnosing security flow issues
- Diagnosing data transformation issues
The z/OS Connect EE team have taken that feedback on board and will be using it to help shape the design for future iterations of the product, where we hope to eliminate these issues. If you are interested in joining us to help shape the user experience design in these areas for future product versions, please sign up to the Z Client Feedback program via the link below, indicating your interest in z/OS Connect EE:
https://www-01.ibm.com/marketing/iwm/iwmdocs/web/cc/earlyprograms/zcustomer.shtml
Unfortunately this RFE is quite specific about the solution, and, the solution described would not be entirely practical or effective given our future direction. As such, to avoid confusion, we will be declining this RFE at this time. However, if you would like to raise a more general requirement for improving the diagnostics and support user experience, that would be helpful to allow us to have a more transparent and open conversation with the community.
Whether or not you choose to raise a new RFE, rest assured that your feedback has been heard and we will endeavour to improve the usability around diagnostics going forward.
Of course the other benefit of limiting the trace by target is hopefully less impact from tracing. The standard set of traces normally requested would cripple a production system due to their overhead.
I seem to be in traces for just about every issue we may encounter in zOS Connect, from authentication issues to data transformation ones. The traces provide more insight into the issue such as the token being passed, the data the transformation fails with etc etc.
Even if you only want to use them for IBM support being able to limit the volume of trace data in the shared high volume environments would be of benefit.
Thank you for your response.
We would like to know what kind of issues you are trying to diagnose?
Trace is intended primarily as a tool for IBM support. If we can understand more about the issue you are having difficulty resolving using more user focused approaches (eg, messages, monitoring etc) it will help us to better understand how best to address the requirement.
B
with high volume systems huge amounts of trace data can be produced, anything that can limit/target the data to specific API would be beneficial.
Thank you for this requirement.
To help us better evaluate the need, it would be great if those who have voted on this RFE could clarify the use case for "Individual API trace". Specifically we would like to know if this capability is needed because:
A) You are having difficulty collecting trace for IBM support when dealing with a case.
OR
B) You are having difficulty diagnosing API issues yourself.
We would appreciate it if you could respond with a comment specifying either A, B or Both. In each case some detail as to what is specifically causing the difficulty would be appreciated.