Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Workspace z/OS Connect
Created by Guest
Created on Sep 20, 2024

Enable tracing per API on zOS Connect OAS 3

Given that when enabling tracing (either binary or non binary), there's an impact on server performance, that affects all APIs deployed on that server, we'd like to have an option to enable tracing per api, so that when analyzing we'll only be impacting the problematic API and not all of them.

Idea priority High
  • Admin
    Demelza Farrer
    Reply
    |
    Dec 5, 2024

    Unfortunately there was not enough information to allow us to effectively assess this

    requirement. In a previous comment we requested the information that would help us

    clarify key points, but this information has not been provided.

    Regreably this means that we cannot effectively assess this requirement and so our

    only option is to declined it at this point. You are free to re-raise this requirement

    with the detail requested if you still want it to be considered.

  • Admin
    Demelza Farrer
    Reply
    |
    Nov 19, 2024

    trace is not for customer use. If you require monitoring information for a single API please detail what specific monitoring information is required

  • Admin
    Demelza Farrer
    Reply
    |
    Oct 15, 2024

    Thanks Melina,

    Please can you further explain what the tracing is specifically for and how it will be used ?

  • Admin
    Demelza Farrer
    Reply
    |
    Oct 1, 2024

    Unfortunately there was not enough information to allow us to effectively assess this requirement. It would be helpful if you could clarify some key points.

    Please provide details of the use case the customer has for this requirement. The reasons for doing this and the information you are trying to get out.