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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Decision taken in 3iab on 16 October 2024.
We don’t have any near-term plans to introduce support for Flink ML. However, we are going to bookmark your request for Python support and monitor future requests from other customers as well - as of today, we don't have enough customers pushing to traction this request.
This idea will be marked as "Not Under Consideration".
We have received an update to this idea from the AMEX team.
The EP team will be taking this up in the next 3iab for further discussion.
See response below
EVI-I-132 addresses AMEX’s need to identify single metric anomalies. However, we also need to identify anomalies associated with correlated multiple metrics (ex. Memory vs Response times). If Flink ML is not going to be supported, then we will need the capability to build our own custom operators in Python. We are currently testing multiple ML algorithms to determine which options actually work best with our data.
Within Event Processing we are focused on integrating with externally hosted ML models, where the models are running with tooling to monitor accuracy and drift - an important consideration when operationalising ML models. Flink ML is an extension to Flink is maturing, but doesn't currently make operationalising models easy, hence isn't part of our near term roadmap. Ideas has been marked as "Not Under Consideration."