Skip to Main Content
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
  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 Submitted
Workspace API Connect
Created by Guest
Created on Dec 10, 2024

Add the ability to turn on DataPower Probe for a single API or even a single API Operation

Within our DataPowers in use for SOAP traffic we're able to turn on Probe in DataPower for a single Web Service Proxy to capture http requests and responses for that specific Web Service Proxy. Within DataPowers controlled by API Connect for REST APIs however we lack that ability. For example, when we're investigating a http status code 500 a client receives, we are now often 'forced' to turn on debug level trace logging for the entire DataPower and only then do we have visible trace records of what went wrong where. On a higher volume system switching to debug level trace logging is no longer an option.

Idea priority Medium