IBM Data and AI RegTech Ideas Portal

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

Shorter URL for this site is: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas

Status Not under consideration
Created by Guest
Created on Apr 30, 2021

FTM for eTransfer - Configurable probes and timeout values

In the current FTM for Interac e-Trasfers 4.0.3 application that we have running, we had issues with probe failures and timeouts resulting in pods restarting. The issue was sometimes with Aqua, sometimes with Dynatrace or it could be application related too. But, if we have options to configure probes, timeouts and other configuration related to the readiness and liveness probes, it will help us to change it incase we run into issues. So, the ask is to have these configurations of probe to be changed by application team if required.

  • Admin
    Craig Rector
    Jul 14, 2021

    IBM has made changes to FTM for OpenShift to remove the friction with Dynatrace, therefore addressing the root cause as we agree with the assertion we can't have pods restarting, etc. due to probe issues. But with that said, we have no plans to provide configurable probe and timeout values due to the complexity that would introduce. I am happy to discuss this situation if the pod restart issues persist, but we believe that has been addressed with the http approach that replaced the previous script approach.