Integration
Hide about this portal
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
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 Bernhard for providing those links.
The issue with Gateway Processing status is that it lists the previous x changes of the last y minutes.
What we require is: is API a published on all gateway pods under version v? yes or no
Writing any kind of "watcher service" that watches this stream of changes from the Gateway Processing Status and translate it to our requirements is problematic:
Gateway Processing status only stores the information for a limited amount of minutes: This watcher service must watch the Gateway processing status constantly and is not allowed to miss any changes, otherwise the change status to the new version will be provided as "no" since the event has never been seen
This watcher service must be HA since our pipeline is. Hence 3 replicas have to communicate with each other to sync up the stuff which they have seen
some kind of persistence is need to store this information:
e.g. the service must restart: even after a restart, the watcher service must be able to tell if API a was published under version v
such information if API a was published under version v must be stored in a persistent manner: publishing times from API Manager to Gateways have been slowly but steadily increasing due to increased publishing lifecycle-load so that a publish-event on API Manager can take 30+ min to sync up within the Gateways. We even had a case/incident were it took several hours/ maybe even days.
--> introducing any kind of persistence create the room for data drift between our persistent storage and what is actually on the gateways
Overall creating such a service in a serious manner is accompanied with a lot of issues as outlined above.
An API management system is explicitly bought to have such questions already solved and the customer should not be forced to reimplement such logic.
The API manager seems to be listening on this gateway processing status anyways and also understands how it works.
So, providing any kind of endpoint which abstracts this question of "is API a published on all gateway pods under version v?" is the best way.
I think you are searching for https://www.ibm.com/docs/en/api-connect/10.0.5.x_lts?topic=cloud-reviewing-gateways-processing-status#tapic_gw_status_cli
This is also present in provider api https://apic-api.apiconnect.ibmcloud.com/v10/#/IBMAPIConnectPlatformProviderAPI_200/operation/%2Fcatalogs%2F%7Borg%7D%2F%7Bcatalog%7D%2Fconfigured-gateway-services%2F%7Bconfigured-gateway-service%7D/get
I think you are searching for https://www.ibm.com/docs/en/api-connect/10.0.5.x_lts?topic=cloud-reviewing-gateways-processing-status#tapic_gw_status_cli.
Although it is not mentioned in this documentation, it is also available in provider api (https://apic-api.apiconnect.ibmcloud.com/v10/#/IBMAPIConnectPlatformProviderAPI_200/operation/%2Fcatalogs%2F%7Borg%7D%2F%7Bcatalog%7D%2Fconfigured-gateway-services%2F%7Bconfigured-gateway-service%7D/get)
Kind regards
Bernhard