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.


Add a new idea Subscribe
Status Under review
Workspace API Connect
Created by Guest
Created on May 19, 2025

RELATED IDEAS

API Gateway should log latency informatione for failing policies in API Analytics

Currently latency of failing policies are included in latency of the (otherwise unrelated) preceeding policy. We would like the latency information for a policy that fails in an API assembly to also be visible in API Analytics. This is particularly important for invokes that fail due to timeouts (which can last several minutes). The latency of this specific policy should not be included in the latency of another, unrelated policy.

We have noticed errors in APIs, especially when invokes fail due to timeouts in the invoke policy. In these cases, API Analytics does not display the invoke policy at all. Instead, the latency that was "consumed" during the invoke is incorrectly attributed to the immediately preceding policy. This is misleading because the preceding policy did not take long, while the invoke is completely missing.

 

 

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.