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 Under review
Categories Event Processing
Created by Guest
Created on May 28, 2024

Support for API/ledger source function

IBM Event Automation should support an API/ledger source function where the OTel Collectors can send their streaming data. The API/Ledger component needs to be fully in-memory and have a supported Flink connect.

Idea priority High
  • Admin
    Sam Kunthiparambil
    Reply
    |
    Aug 28, 2024

    The client is essentially asking for http source connector. Until now, our source is Kafka topics only, this customer wants to make API calls as source. We have a http connector as of now for making API enrichments, but client wants to tweak it.

    If we do this, we would be encroaching heavily into App Connect. So, this one needs to go into strategic fit discussions rather than a straightforward implementation. By consensus, the team voted to not go ahead with this. Idea has been marked as "Not Under Consideration."