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 Oct 7, 2026

API Connect - DataPower Liveness Probe - Use /webapi-init-check

Background:

It seems that by default, API Connect is using /healthz and the liveness probe health check endpoint.  This returns ready prior to all of the DataPower configuration being applied and being fully ready.  This is causing Openshift to send traffic to the (not-yet-ready) DataPower pods, which causes brief, intermittent outages for our clients.

API Connect has a /webapi-init-check endpoint that only returns ready once all of the configuration has been applied.

 

Request:

Update API Connect to configure the DataPowerService to use the /webapi-init-check health check endpoint instead of the /healthz endpoint.

 

Links:

https://www.ibm.com/docs/en/datapower-operator/1.18.x?topic=spec-readinessprobe
"As a best-practice, the readinessProbe should be customized such that it probes a real service within your DataPower configuration. This way, the DataPower pods will not become Ready and begin to receive traffic until the service being probed is up and handling requests."

 

https://www.ibm.com/support/pages/how-properly-health-check-api-connect-gateway?view=full
"The API gateway (which handles client API requests) also has a built-in URI: https://apigw:9443/webapi-init-check
This URI returns HTTP 200 when all the catalogs have been loaded. This is the preferred way to check if the gateway is ready to take traffic."

 

Idea priority Medium